# CVE-2026-1950: No checking of the length of the buffer with the file name in AS320T

> A buffer overflow in Delta AS320T allows attackers to execute arbitrary code or cause denial of service via crafted file names.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2026
- **Updated:** 24 Apr 2026
- **Also known as:** GHSA-wv29-5pf5-8fp6

## What is CVE-2026-1950?

CVE-2026-1950 is a critical memory corruption vulnerability in DeltaWW AS320T, published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Delta Electronics AS320T has 
No checking of the length of the buffer with the file name vulnerability.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2026-1950?

It affects 1 product.


Products: Deltaww As320t Firmware.

## How do I fix CVE-2026-1950?

No fix has been published for CVE-2026-1950 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-1950 being exploited?

There is no known exploitation of CVE-2026-1950 in the wild and no public exploit code.

## Other vulnerabilities in DeltaWW AS320T

- [CVE-2026-1949](https://insights.sbomify.com/CVE-2026-1949/): Incorrect calculation of buffer size on the stack in AS320T (critical 9.8)
- [CVE-2026-1951](https://insights.sbomify.com/CVE-2026-1951/): No checking of the length of the buffer with the directory name in AS320T (critical 9.8)
- [CVE-2026-1952](https://insights.sbomify.com/CVE-2026-1952/): Denial of service via the undocumented subfunction in AS320T (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1950 and fix it if it is affected.

What it is: CVE-2026-1950 is a critical memory corruption vulnerability in DeltaWW AS320T, published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1950 in the wild and no public exploit code.

Affected product: DeltaWW AS320T. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1950/ (Markdown: https://insights.sbomify.com/CVE-2026-1950/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1950
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1950
- OSV: https://osv.dev/vulnerability/CVE-2026-1950

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1950/
Summaries are generated and may contain mistakes; the official description above is the record.