CVE-2026-1951
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDelta Electronics AS320T has no checking of the length of the buffer with the directory name vulnerability.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceBuffer overflow vulnerability in Delta Electronics AS320T industrial controller where the directory name handling routine lacks proper bounds checking, allowing a buffer to be overrun. This could enable remote attackers to execute arbitrary code due to the critical CVSS score of 9.8.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.12CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify AS320T controller on the networkLocate Delta Electronics AS320T devices using network scanning, asset inventory, or by accessing the controller's web interface or management console. Note the device's IP address and confirm the model number displays as AS320T.Affected if A Delta Electronics AS320T controller is present in the environment.
-
Check installed firmware versionAccess the controller's administration interface (typically via web browser or serial console), navigate to the system information or firmware version page, and record the displayed firmware version number.Affected if The installed firmware version is earlier than 1.12 (for example, 1.10, 1.11, or any version number less than 1.12).
-
Verify directory name handling feature availabilityLocate the directory management or file browser functionality within the controller's web interface or API. This feature allows users to create, rename, or manage directories/folders on the controller's file system.Affected if The directory management feature is enabled or accessible on the controller.
-
Confirm network exposure of management interfaceCheck the network configuration to determine if the controller's management interface (HTTP/HTTPS ports) is accessible from untrusted network segments or directly from the internet. Review firewall rules and access control lists.Affected if The controller's management interface is reachable from untrusted networks without proper network segmentation or access controls.
A user is affected if they have a Delta Electronics AS320T controller running firmware version 1.12 or lower with the directory management feature accessible, particularly if exposed to untrusted networks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.12
Contact Delta Electronics for the official firmware/security patch for the AS320T and apply it following vendor guidance. If no patch exists, implement network segmentation and access controls to limit exposure to untrusted networks.
AS320T Firmware version 1.12
- Obtain the AS320T firmware version 1.12 or later from the vendor's official support site (filecenter.deltaww.com)
- Follow Delta Electronics standard firmware update procedure for the AS320T device
- Verify the firmware version has been successfully updated to 1.12 or later after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,944.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1951 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1951 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data