dbcve.org
As320t FirmwareOperating system · Deltaww

CVE-2026-1952

HIGH · 7.5 CVSS v3.1 Published 2026-04-24
Fix available
A fix is available. Upgrade to 1.16 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Delta Electronics AS320T has denial of service via the undocumented subfunction 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 confidence

The Delta Electronics AS320T industrial controller contains an undocumented subfunction that can be triggered to cause denial of service. The vulnerability is network-exploitable without authentication and results in complete availability impact, likely causing the device to crash or become unresponsive.

MitigationApply vendor firmware updates when available; until then, restrict network access to the AS320T device using firewalls or network segmentation to limit exposure to unauthenticated attackers.

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
As320t FirmwareOperating system
Affected:< 1.16

CVSS 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify AS320T firmware version
    Access the device management interface or use the vendor's diagnostic tool to retrieve the current firmware version. Common methods include logging into the device web interface, using Delta's configuration software, or checking the device status page.
    Affected if Firmware version is below 1.16 (any version prior to 1.16 is affected)
  2. Confirm device is network accessible
    Verify the AS320T has an active IP address and is reachable on the network by pinging the device or checking network connectivity status through the controller's interface.
    Affected if The device is network-accessible and responds to network requests
  3. Verify unauthenticated network access exposure
    Determine if the device's management interface or industrial protocols are exposed to network segments that contain untrusted users. Check firewall rules, VLAN segmentation, and whether the device accepts connections from any network address without authentication.
    Affected if The device accepts network connections from untrusted networks without requiring authentication
  4. Check for device availability anomalies
    Monitor the device for unexpected crashes, unresponsiveness, or restart cycles. Review any available system logs or status indicators for signs of instability or denial of service events.
    Affected if Device exhibits frequent crashes, hangs, or requires frequent reboots

The environment is affected if the AS320T device is running firmware version below 1.16 and is accessible on a network where unauthenticated attackers can reach it, as the undocumented subfunction can be triggered remotely without credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.16 or later
Fixed in 1.16
Interim mitigation

Apply vendor firmware updates when available; until then, restrict network access to the AS320T device using firewalls or network segmentation to limit exposure to unauthenticated attackers.

Recommended fix Moderate confidence

Firmware version 1.16

  1. 1. Identify the current firmware version of the Delta Electronics AS320T device
  2. 2. Navigate to the vendor's firmware download page at filecenter.deltaww.com
  3. 3. Download firmware version 1.16 or later for the AS320T model
  4. 4. Access the device's web management interface or firmware update utility
  5. 5. Upload and apply the firmware version 1.16 file following the vendor's documented upgrade procedure
  6. 6. Allow the device to complete the firmware update and reboot process
  7. 7. Verify the firmware has been successfully updated to version 1.16 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in As320t Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1952 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1952 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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