Code execution via unvalidated DSB parser write
Published Sep 3, 2026 · Updated Sep 4, 2026
Out-of-bounds write in Digilent DASYLab before 2026.0.0 allows attackers to execute code after a user opens a crafted .DSB file. The DSB parser fails to validate user-supplied data before writing it, causing a write past the end of an allocated data structure. A user must open the file, after which memory corruption can execute attacker-controlled code in that user's context.
Summary
What happened
Out-of-bounds write in Digilent DASYLab before 2026.0.0 allows attackers to execute code after a user opens a crafted .DSB file. The DSB parser fails to validate user-supplied data before writing it, causing a write past the end of an allocated data structure. A user must open the file, after which memory corruption can execute attacker-controlled code in that user's context.
The record
- CVE
- CVE-2026-64197
- Published
- Sep 3, 2026
- Updated
- Sep 4, 2026
- Vendor
- Digilent
- Product
- DASYLab
- Classifications
- CWE-787, CAPEC-100, T1204.002
- 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