Out Of Bounds Write when parsing a .DSB file in DASYLab due to improper validation of user-supplied data, resulting in a write past the end of an allocated heap

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps measX/DASYLab (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for measX/DASYLab.
2. 2Review the reported fix. Update measX/DASYLab to 2026.0.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Sep 3, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 3, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 3, 2026

Sources and claim methodology

• Source referencemeasx.com

Related CVEs

• Out Of Bounds Write parsing a .DSB file in DASYLab due to lack of proper validation of user-supplied dataSame measx/dasylab package
• Out Of Bounds Write when parsing a .DSB file in DASYLab due to improper validation of user-supplied data, resulting in a write past the end of an allocated data structureSame measx/dasylab package
• Out Of Bounds Read in file handling when parsing a .DSB file in DASYLabSame measx/dasylab package
• Out Of Bounds Read outside the bounds of an allocated data structure when parsing a .DSB file in DASYLabSame measx/dasylab package
• Out Of Bounds Read in during string conversionwhen parsing a .DSB file in DASYLabSame measx/dasylab package
• MOOS-IvP through 24.8.1 Buffer Overflow in IvP Function String DecodersAlso CWE-787