CVE-2026-1950 json
No checking of the length of the buffer with the file name in AS320T
published 6mo ago modified 14d ago also EUVD-2026-25402
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
Delta Electronics AS320T has No checking of the length of the buffer with the file name vulnerability.
Patch / fix
- deltaww as320t_firmware 1.16
Is CVE-2026-1950 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 6mo ago
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- DeltaWW AS320T
Classification
- Weakness
-
- CWE-121 Stack-based Buffer Overflow
References
Sources
- CVE List CVE-2026-1950
- NVD CVE-2026-1950
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.