Quick answers
- Is CVE-2026-64196 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-64196 being exploited in the wild.
- How severe is CVE-2026-64196?
- High severity, with a CVSS score of 7.8, published 3 September 2026.
- Which products and versions are affected?
- measX DASYLab before 2026.0.0 (Build 65).
- Is there a fix for CVE-2026-64196?
- A patch was published on 2026-09-03: Fixed in DASYLab 2026.0.0 (Build 65) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-64196 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-64196?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
These are out-of-bounds write vulnerabilities (CWE-787) in DASYLab's DSB file parser caused by improper validation of user-supplied data in file structures. The vulnerabilities result in heap buffer overflows when parsing specially crafted DSB files. Attack requires local delivery of a malicious DSB file and user interaction to open it; the vulnerabilities are not remotely exploitable. Successful exploitation allows arbitrary code execution in the context of the affected application. The vulnerabilities affect all DASYLab versions before 2026.0.0 (Build 65) and are resolved in that version and later.
Affected products
- measX DASYLab before 2026.0.0 (Build 65)
Timeline
- 2026-08-17: disclosed
- 2026-09-03: patched: Fixed in DASYLab 2026.0.0 (Build 65)
- 2026-09-03: advisory