CVE-2026-64196 Memory corruption in DASYLab
An attacker can execute arbitrary code by tricking a user into opening a malicious .DSB file in DASYLab due to an out-of-bounds write vulnerability.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-64196?
CVE-2026-64196 is a high-severity memory corruption vulnerability in measX DASYLab, published on 3 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official description
There is an out-of-bounds write vulnerability in DASYLab due to improper validation of user-supplied data, resulting in a write past the end of an allocated heap. Successful exploitation requires an attacker to get a user to open a specially crafted .DSB file. This issue affects all versions before 2026.0.0.
Weakness: CWE-787
Which versions are affected by CVE-2026-64196?
It affects 1 product.
Products include Ni Dasylab.
How do I fix CVE-2026-64196?
No fix has been published for CVE-2026-64196 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2026-64196 being exploited?
There is no known exploitation of CVE-2026-64196 in the wild and no public exploit code.
Other vulnerabilities in measX DASYLab
- CVE-2026-64199 Out Of Bounds Read outside the bounds of an allocated data structure when parsing a .DSB file in DASYLab
- CVE-2026-64195 Out Of Bounds Write parsing a .DSB file in DASYLab due to lack of proper validation of user-supplied data
- CVE-2026-64197 Memory corruption in DASYLab
- CVE-2026-64198 Out Of Bounds Read in file handling when parsing a .DSB file in DASYLab
- CVE-2026-64200 Out Of Bounds Read in during string conversionwhen parsing a .DSB file in DASYLab
Sources
Also known as GHSA-v5qj-5q4r-8fg9.