Quick answers
- Is CVE-2026-64198 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-64198 being exploited in the wild.
- How severe is CVE-2026-64198?
- 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-64198?
- 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-64198 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-64198?
- 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
CVE-2026-64198 is an out-of-bounds read vulnerability (CWE-125) in DASYLab's DSB file parser caused by improper validation of user-supplied data. The vulnerability occurs during file handling when parsing specially crafted DSB files, resulting in reads a few bytes past the end of an allocated heap buffer. The attack vector is local and requires user interaction—an attacker must trick a user into opening a malicious DSB file. Successful exploitation can result in information disclosure or arbitrary code execution in the context of the DASYLab process. The vulnerability is fixed in DASYLab version 2026.0.0 (Build 65) 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)