Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Critical · CVSS 9.8

How to Fix CVE-2026-1950: AS320T (Bundle Sibling)

By Sai Kiran Pandrala

Last verified: 2026-05-25

CVE-2026-1950 is a sibling vulnerability in the same vendor advisory as CVE-2026-1949. Applying the patched build named in the primary write-up closes this CVE as well.

⚡ At a glance
SeverityCVSS 9.8 - Critical
Actively exploited?Not currently in CISA KEV
AffectedSame as the bundle - see CVE-2026-1949
Fixed inSame patched build as CVE-2026-1949 (See vendor advisory)
Type (CWE)CWE-121: CWE-121 Stack-based Buffer Overflow

What's different about CVE-2026-1950?

Delta Electronics AS320T has

No checking of the length of the buffer with the file name vulnerability.

The technical impact and remediation are identical to the primary CVE in the bundle. The same vendor patch closes both.

How to fix CVE-2026-1950

Apply the patched build per the primary write-up: How to Fix CVE-2026-1949.

The patch installation procedure, verification commands, and interim mitigations are documented there. Reusing one runbook keeps the rollout consistent across the bundle.

Frequently asked questions

Is CVE-2026-1950 fixed by the same patch as CVE-2026-1949?

Yes. CVE-2026-1950 ships in the same vendor advisory as CVE-2026-1949. Applying the patched build named in the primary write-up closes both.

What is the CVSS score for CVE-2026-1950?

The CVSS base score is 9.8 (Critical).

Is it being exploited?

It is not currently listed in CISA KEV.

References


*Part of the AS320T bundle. Full procedure at CVE-2026-1949.*