Out-of-Bounds Write Vulnerabilities in DASYLab

Created Aug 17, 2026

Overview

There are multiple out-of-bounds write vulnerabilities when parsing user-supplied files in DASYLab that may result in information disclosure or arbitrary code execution. Successful exploitation requires a user to open a specially crafted DSB file, and these vulnerabilities affect all versions of DASYLab before 2026.0.0 (Build 65).

This advisory covers CVE-2026-64195, CVE-2026-64196, and CVE-2026-64197.

Contents

Mitigation Guidance

These issues are resolved in DASYLab 2026.0.0 (Build 65). measX recommends that users update to DASYLab 2026.0.0 (Build 65) or later and avoid opening DASYLab or DSB files from untrusted sources. Exploitation requires local user interaction in that the user must open a malicious DSB file, and the issues are not exploitable remotely.

Affected Products

Product VersionMitigation
DASYLab – all versions before 2026.0.0 (Build 65) Update to DASYLab 2026.0.0 (Build 65) or later; avoid opening untrusted DASYLab or DSB files
DASYLab 2026.0.0 (Build 65) Not affected

CVSS Score

All three issues are classified as CWE-787 (Out-of-bounds Write).

Further Information

The vulnerabilities were reported against DASYLab 2024 (17.0.0), Build 20, and confirmed on Windows 10 22H2 x64.

CVE-2026-64195 is an out-of-bounds write in DSB file parsing caused by lack of proper validation of user-supplied data, resulting in a write past the end of an allocated heap buffer.

CVE-2026-64196 is an out-of-bounds write in DSB file parsing caused by improper validation of user-supplied data, resulting in a write past the end of an allocated heap buffer; the condition is classified as exploitable.

CVE-2026-64197 is an out-of-bounds write in DSB file parsing caused by improper validation of user-supplied data, resulting in a write past the end of an allocated data structure; the condition is classified as exploitable.

All three vulnerabilities can allow an attacker to execute code in the context of the current process if a user opens a malicious DSB file.

Acknowledgements

measX credits Michael Heinzl for reporting these issues and coordinating disclosure.

Additional Resources