PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-42477 Opencascade CVE debrief

CVE-2026-42477 affects Open CASCADE Technology (OCCT) OBJ file parsing and is triggered when a victim opens a crafted OBJ file. The issue is a heap-based out-of-bounds read in RWObj_Reader::read, which can lead to denial of service and may expose sensitive information. NVD maps the issue to OCCT versions up through 7.9.3 and the 8.0.0 beta/RC line through rc5, with a published date of 2026-05-01 and a later modification on 2026-05-10.

Vendor
Opencascade
Product
Open Cascade Technology
CVSS
HIGH 7.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-05-01
Original CVE updated
2026-05-10
Advisory published
2026-05-01
Advisory updated
2026-05-10

Who should care

Organizations and developers that use OCCT to import or process OBJ files, especially where files can come from untrusted or user-supplied sources. Security teams should also care if OCCT is embedded in CAD, visualization, or conversion workflows that accept external geometry files.

Technical summary

According to the CVE description, Standard_ReadLineBuffer::ReadLine() can return a 1-byte buffer for a minimal OBJ line, and RWObj_Reader::read() then calls pushIndices(aLine + 2) without checking that the buffer is long enough. That creates a heap-based out-of-bounds read (CWE-125, with CWE-122 also listed as secondary) during OBJ parsing. NVD reports CVSS 3.1 vector AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H, reflecting a local impact that requires user interaction to open the crafted file.

Defensive priority

High. The vulnerability requires user interaction, but it affects file parsing of a common interchange format and can expose data or crash the process. If your environment handles untrusted OBJ files, mitigation and update planning should be prioritized.

Recommended defensive actions

  • Identify all uses of Open CASCADE Technology in applications, services, plugins, and conversion pipelines that parse OBJ files.
  • Restrict or sandbox handling of untrusted OBJ files until patched versions are available.
  • Check vendor and downstream release channels for a fixed OCCT release; the supplied sources do not include a remediation version.
  • If you maintain a fork or wrapper around OCCT, add explicit length checks before advancing pointers into line buffers and review adjacent OBJ parsing logic.
  • Monitor the official CVE and NVD records for updates, including any future fix references or version clarifications.
  • Treat unexpectedly small or malformed OBJ lines as invalid input in any application-layer validation or pre-processing stage.

Evidence notes

This debrief is based on the supplied CVE description and NVD metadata. The source corpus states a heap-based out-of-bounds read in RWObj_Reader::read caused by pointer arithmetic on a potentially 1-byte buffer returned by Standard_ReadLineBuffer::ReadLine(). NVD lists affected OCCT versions through 7.9.3 and 8.0.0 beta1 through rc5, and assigns CVSS 3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H. No vendor patch announcement or fixed version is included in the supplied sources.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-42477 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-42477

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-42477 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-42477

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.