# CVE-2026-64199: Out Of Bounds Read outside the bounds of an allocated data structure when parsing a .DSB file in DASYLab

> An attacker can cause an out-of-bounds read by tricking a user into opening a malicious .DSB file, potentially leading to crashes or data exposure.

- **Severity:** High 8.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** GHSA-phqm-v98p-hr87

## What is CVE-2026-64199?

CVE-2026-64199 is a high-severity memory corruption vulnerability in measX DASYLab, published on 3 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There is an out-of-bounds read vulnerability in DASYLab due to improper validation of user-supplied data.   This results in a read outside the bounds of an allocated data structure.  Successful exploitation requires an attacker to get a user to open a specially crafted .DSB file.  This issue affects all versions before 2026.0.0.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-64199?

It affects 1 product.


Products: Ni Dasylab.

## How do I fix CVE-2026-64199?

No fix has been published for CVE-2026-64199 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-64199 being exploited?

There is no known exploitation of CVE-2026-64199 in the wild and no public exploit code.

## Other vulnerabilities in measX DASYLab

- [CVE-2026-64195](https://insights.sbomify.com/CVE-2026-64195/): Out Of Bounds Write parsing a .DSB file in DASYLab due to lack of proper validation of user-supplied data (high 8.5)
- [CVE-2026-64196](https://insights.sbomify.com/CVE-2026-64196/): Memory corruption in DASYLab (high 8.5)
- [CVE-2026-64197](https://insights.sbomify.com/CVE-2026-64197/): Memory corruption in DASYLab (high 8.5)
- [CVE-2026-64198](https://insights.sbomify.com/CVE-2026-64198/): Out Of Bounds Read in file handling when parsing a .DSB file in DASYLab (high 8.5)
- [CVE-2026-64200](https://insights.sbomify.com/CVE-2026-64200/): Out Of Bounds Read in during string conversionwhen parsing a .DSB file in DASYLab (high 8.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64199 and fix it if it is affected.

What it is: CVE-2026-64199 is a high-severity memory corruption vulnerability in measX DASYLab, published on 3 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-64199 in the wild and no public exploit code.

Affected product: measX DASYLab. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-64199/ (Markdown: https://insights.sbomify.com/CVE-2026-64199/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-64199
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-64199
- OSV: https://osv.dev/vulnerability/CVE-2026-64199

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-64199/
Summaries are generated and may contain mistakes; the official description above is the record.