dbcve.org
As320t FirmwareOperating system · Deltaww

CVE-2026-1949

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-24
Fix available
A fix is available. Upgrade to 1.16 or later.
See remediation →
100/100
Remediation priority · Urgent
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 incorrect calculation of the buffer size on the stack in the GET/PUT request handler of the web service.

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

Stack-based buffer overflow in the GET/PUT request handler of the AS320T web service due to incorrect buffer size calculation. This memory corruption vulnerability with CVSS 9.8 is likely exploitable for remote code execution without authentication.

MitigationIf available, apply vendor firmware update; otherwise, isolate the device on a restricted network segment and disable external web service access until a patch is released.

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
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 checks

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

  1. Identify the device model
    Access the device web interface or check the device label/metadata to confirm it is a Deltaww AS320T storage device
    Affected if Device is not an AS320T model
  2. Check the installed firmware version
    Log into the web interface and navigate to System Settings > Firmware Version, or check via SNMP/CLI if available. Compare the version number to 1.16
    Affected if Firmware version is below 1.16 (e.g., 1.15, 1.14, etc.)
  3. Verify the web service is enabled
    Check the device network settings or services configuration to confirm the web service/HTTP server is turned on
    Affected if Web service is enabled and accessible on the network
  4. Confirm web service is network-accessible
    Attempt to access the device HTTP/HTTPS interface from a remote host or check firewall rules: curl http://[device-ip] or curl https://[device-ip]
    Affected if The web interface is reachable from a network segment where attackers could send GET/PUT requests

The environment is affected if the device is a Deltaww AS320T running firmware version below 1.16 with the web service enabled and accessible on the network.

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.

From vendor data
Upgrade available Upgrade to 1.16 or later
Fixed in 1.16
Interim mitigation

If available, apply vendor firmware update; otherwise, isolate the device on a restricted network segment and disable external web service access until a patch is released.

Fix this in As320t Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1949 — 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-1949 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