Memory corruption via unchecked directory-name length
Published Apr 24, 2026 · Updated Apr 24, 2026
Stack-based buffer overflow in Delta Electronics AS320T 1.10 and earlier allows remote attackers to corrupt memory via a directory name. The firmware processes a directory name without checking its length before placing it in a stack buffer; Delta has not identified the handler or copy operation. Network access is sufficient, with no authentication or user interaction required; Delta has not disclosed whether exploitation causes a crash or code execution.
Summary
What happened
Stack-based buffer overflow in Delta Electronics AS320T 1.10 and earlier allows remote attackers to corrupt memory via a directory name. The firmware processes a directory name without checking its length before placing it in a stack buffer; Delta has not identified the handler or copy operation. Network access is sufficient, with no authentication or user interaction required; Delta has not disclosed whether exploitation causes a crash or code execution.
The record
- CVE
- CVE-2026-1951
- Published
- Apr 24, 2026
- Updated
- Apr 24, 2026
- Vendor
- Delta Electronics, Inc.
- Product
- AS320T
- Classifications
- CWE-121, CAPEC-100, T0866
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 24, 2026CVE publishedPublication date reported by the CVE source.
- Apr 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo