CVE-2026-64198
Out-of-bounds read in DASYLab when opening crafted .DSB files
Is CVE-2026-64198 being exploited?
Not confirmed. CVE-2026-64198 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.12% probability of exploitation in the next 30 days.
How severe is CVE-2026-64198?
CVE-2026-64198 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-64198?
Yes. A fix has been recorded for CVE-2026-64198. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64198 affect?
CVE-2026-64198 affects DASYLab < 2026.0.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64198?
Update DASYLab to 2026.0.0 or later and avoid opening untrusted .DSB files
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Opening a malicious .DSB triggers an out-of-bounds heap read, enabling memory disclosure or app crash (DoS).
Patch when possible
- affected< 2026.0.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.