CVE-2026-42479
Out-of-Bounds Read in Open CASCADE Technology VRML Parser
Publication date: 2026-05-01
Last updated on: 2026-05-01
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| opencascade | open_cascade_technology | to 7.9.3 (inc) |
| opencascade | open_cascade_technology | 8.0.0 |
| opencascade | open_cascade_technology | 8.0.0 |
| opencascade | open_cascade_technology | 8.0.0 |
| opencascade | open_cascade_technology | 8.0.0 |
| opencascade | open_cascade_technology | 8.0.0 |
| opencascade | open_cascade_technology | 8.0.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-125 | The product reads data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, ensure that the software version of Open CASCADE Technology (OCCT) you are using is updated to a version where the out-of-bounds read issue in the VRML parser is fixed.
The root cause involves lack of validation of coordIndex values against the size of the coordinate array during geometry processing. Applying patches or updates that add proper validation will prevent the denial of service.
Avoid processing untrusted or crafted VRML files until the fix is applied.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
There is no specific information provided about detection methods or commands to identify this vulnerability (CVE-2026-42479) on a network or system.
Can you explain this vulnerability to me?
This vulnerability is an out-of-bounds read in the VRML parser component of Open CASCADE Technology (OCCT) version V8_0_0_rc5. Specifically, it occurs in the VrmlData_IndexedLineSet::TShape function, where coordIndex values from a parsed VRML file are used as array indices without checking if they are within the valid range of the coordinate array. This lack of validation can lead to reading memory outside the intended bounds.
How can this vulnerability impact me? :
The primary impact of this vulnerability is that an attacker can cause a denial of service (DoS) by providing a specially crafted VRML file. This crafted file triggers the out-of-bounds read, which can crash the application or cause it to behave unexpectedly, potentially disrupting normal operations.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.