CVE-2026-42476

May 1, 2026, 7:16 p.m.

7.1
High

Description

Two heap-based out-of-bounds read vulnerabilities in the STL ASCII file parser in Open CASCADE Technology (OCCT) V8_0_0_rc5 exist in RWStl_Reader::ReadAscii because buffers returned by Standard_ReadLineBuffer::ReadLine() are not properly length-validated before strncasecmp or direct byte access. User-assisted attackers can trigger these issues by persuading a victim to open a crafted STL file with extremely short lines, resulting in a denial of service or possible information disclosure.

Product(s) Impacted

Vendor Product Versions
Opencascade
  • Open Cascade Technology
  • *, 8.0.0

Weaknesses

Common security weaknesses mapped to this vulnerability.

CWE-125
Out-of-bounds Read
The product reads data past the end, or before the beginning, of the intended buffer.

*CPE(s)

Affected systems and software identified for this CVE.

Type Vendor Product Version Update Edition Language Software Edition Target Software Target Hardware Other Information
a opencascade open_cascade_technology / / / / / / / /
a opencascade open_cascade_technology 8.0.0 beta1 / / / / / /
a opencascade open_cascade_technology 8.0.0 rc1 / / / / / /
a opencascade open_cascade_technology 8.0.0 rc2 / / / / / /
a opencascade open_cascade_technology 8.0.0 rc3 / / / / / /
a opencascade open_cascade_technology 8.0.0 rc4 / / / / / /
a opencascade open_cascade_technology 8.0.0 rc5 / / / / / /

CVSS Score

7.1 / 10

CVSS Data - 3.1

  • Attack Vector: LOCAL
  • Attack Complexity: LOW
  • Privileges Required: NONE
  • Scope: UNCHANGED
  • Confidentiality Impact: HIGH
  • Integrity Impact: NONE
  • Availability Impact: HIGH
  • CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H

    View Vector String

Timeline

Published: May 1, 2026, 3:16 p.m.
Last Modified: May 1, 2026, 7:16 p.m.

Status : Modified

CVE has been marked for Analysis. Normally once in this state the CVE will be analyzed by NVD staff within 24 hours.

More info

*Disclaimer: Some vulnerabilities do not have an associated CPE. To enhance the data, we use AI to infer CPEs based on CVE details. This is an automated process and might not always be accurate.