Out-of-Bounds Read Vulnerabilities in DASYLab

Created Aug 17, 2026

Overview

There are multiple out-of-bounds read 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-64198, CVE-2026-64199, and CVE-2026-64200.

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-125 (Out-of-bounds Read).

Further Information

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

CVE-2026-64198 is an out-of-bounds read in DSB file parsing caused by lack of proper validation of user-supplied data, resulting in a read a few bytes past the end of an allocated heap buffer during file handling.

CVE-2026-64199 is an out-of-bounds read in DSB file parsing caused by lack of proper validation of user-supplied data, resulting in a read outside the bounds of an allocated data structure.

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

All three vulnerabilities can result in information disclosure, and may 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

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

Deserialization of Untrusted Data Vulnerability in DASYLab

Created Aug 17, 2026

Overview

There is a deserialization of untrusted data vulnerability when parsing user-supplied files in DASYLab that may result in arbitrary code execution. Successful exploitation requires a user to open a specially crafted DSB file, and this vulnerability affects all versions of DASYLab before 2026.0.0 (Build 65).

This advisory covers CVE-2025-9189.

Contents

Mitigation Guidance

This issue is 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 issue is 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

This issue is classified as CWE-502 (Deserialization of Untrusted Data).

Further Information

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

CVE-2025-9189 is a deserialization of untrusted data vulnerability in DASYLab. A Script module embedded in a DSB worksheet stores serialized Python objects (pickle) that are automatically deserialized when the file is opened, allowing an attacker to execute arbitrary code in the context of the current process if a user opens a malicious DSB file.

Acknowledgements

measX credits kimiya, working with Trend Micro Zero Day Initiative, for reporting this issue and coordinating disclosure.

Additional Resources

Created Jun 09, 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 DASYLab or DSB file, and these vulnerabilities affect all versions of DASYLab.

This advisory covers CVE-2026-0954, CVE-2026-0957, and CVE-2025-57778.

Contents

Mitigation Guidance

Update to the current version of DASYLab. For older versions: There are no fixes available for these issues in the referenced advisories. Always: Avoid opening files from untrusted sources.

Affected Products

Product Version

Mitigation

DASYLab – all versions before 2026.0

Avoid opening untrusted DSB files

DASYLab 2026.0

Not affected

CVSS Score

Further Information

CVE-2026-0954 and CVE-2026-0957 are described by NI as out-of-bounds write vulnerabilities when parsing user files in DASYLab. CVE-2025-57778 is described by NVD as an out-of-bounds write vulnerability in DSB file parsing caused by improper bounds checking resulting in an invalid source address.

Acknowledgements

Digilent credited Anonymous, working with Trend Micro Zero Day Initiative, for reporting CVE-2026-0954, and Rocco Calvi (@TecR0c) with TecSecurity, working with Trend Micro Zero Day Initiative, for reporting CVE-2026-0957.

No separate acknowledgement detail was confirmed from the retrieved NVD entry for CVE-2025-57778 beyond the source attribution to National Instruments.

Additional Resources

More Articles ...