Heap corruption via unvalidated DSB file data
Published Sep 3, 2026 · Updated Sep 4, 2026
Out-of-bounds write in DASYLab before 2026.0.0 allows attackers to corrupt heap memory by inducing a user to open a crafted .DSB file. The .DSB parser fails to validate file-supplied data before a heap write, so the write proceeds beyond the allocated buffer's end. Successful exploitation requires a user to open the file; the vendor has not published whether the resulting process-memory corruption ends in a crash or code execution.
Summary
What happened
Out-of-bounds write in DASYLab before 2026.0.0 allows attackers to corrupt heap memory by inducing a user to open a crafted .DSB file. The .DSB parser fails to validate file-supplied data before a heap write, so the write proceeds beyond the allocated buffer's end. Successful exploitation requires a user to open the file; the vendor has not published whether the resulting process-memory corruption ends in a crash or code execution.
The record
- CVE
- CVE-2026-64196
- Published
- Sep 3, 2026
- Updated
- Sep 4, 2026
- Vendor
- Digilent
- Product
- DASYLab
- Classifications
- CWE-787, CAPEC-100, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 3, 2026CVE publishedPublication date reported by the CVE source.
- Sep 4, 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 <2026.0.0
What conditions does exploitation require?
What is affected?
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