CVE-2026-42481
Out-of-Bounds Read and Infinite Recursion in Open CASCADE Technology
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 |
|---|---|---|
| open_cascade_technology | occt | 8.0.0_rc5 |
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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify how the vulnerability in Open CASCADE Technology (OCCT) V8_0_0_rc5 affects compliance with common standards and regulations such as GDPR or HIPAA.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The vulnerability in Open CASCADE Technology (OCCT) V8_0_0_rc5 involves out-of-bounds reads and infinite recursion triggered by crafted IGES or STEP files. Detection can be approached by analyzing the processing of these file types for abnormal behavior such as crashes or memory errors.
One practical method is to use AddressSanitizer (ASAN) or similar memory error detection tools when processing IGES or STEP files with OCCT. ASAN can detect out-of-bounds reads consistently, as demonstrated in related vulnerabilities.
Suggested commands include running OCCT file parsing under ASAN instrumentation, for example:
- Compile OCCT with ASAN enabled: `clang -fsanitize=address -g -o occt_parser your_occt_source_files`
- Run the parser on suspicious or crafted IGES/STEP files: `./occt_parser suspicious_file.iges` or `./occt_parser suspicious_file.step`
Monitoring for crashes, infinite recursion, or memory errors during these tests can help detect the vulnerability.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include avoiding the processing of untrusted or crafted IGES and STEP files with vulnerable versions of OCCT (V8_0_0_rc5).
If possible, update OCCT to a version where these vulnerabilities are fixed or apply patches that validate input lengths and prevent out-of-bounds reads and infinite recursion.
Additionally, running OCCT under memory safety tools like AddressSanitizer during development or testing can help identify and prevent exploitation.
Can you explain this vulnerability to me?
This vulnerability affects Open CASCADE Technology (OCCT) version V8_0_0_rc5 and involves multiple security issues in its IGES and STEP file parsers. Specifically, crafted IGES or STEP files can trigger out-of-bounds reads during B-spline curve evaluation and construction, as well as cause infinite recursion when processing certain self-referential entities. These flaws arise in functions like Geom2d_BSplineCurve::EvalD0, MakeBSplineCurveCommon, and StepShape_OrientedEdge::EdgeStart.
How can this vulnerability impact me? :
Exploiting these vulnerabilities can lead to denial of service conditions, where the affected software may crash or become unresponsive. Additionally, there is a risk of unintended memory disclosure, which could potentially expose sensitive information from the system's memory.