CVE-2026-42478
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in VrmlData_IndexedFaceSet::TShape in the VRML V2.0 parser in Open CASCADE Technology (OCCT) V8_0_0_rc5 allows attackers to cause a denial of service via a crafted VRML file. The issue occurs because malformed VRML input can trigger dereference of a corrupt or unvalidated pointer during shape construction in libTKDEVRML.so.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA pointer dereference vulnerability exists in the VRML V2.0 parser (VrmlData_IndexedFaceSet::TShape) in Open CASCADE Technology V8_0_0_rc5. When parsing a crafted VRML file with malformed input, the parser dereferences a corrupt or unvalidated pointer during shape construction in libTKDEVRML.so, causing a denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 7.9.3= 8.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Open CASCADE Technology installationLocate the OCCT installation directory and find the version file or check the library version strings in libTKDEVRML.so using 'strings' or file version infoAffected if The installed version is <= 7.9.3 or equals 8.0.0 (including release candidate rc5)
-
Verify the VRML library is presentSearch for libTKDEVRML.so in the OCCT lib directory (commonly $CASROOT/linux64/lib or similar) using 'find' or 'ls'Affected if The library file exists, indicating VRML parsing capability is available in this OCCT installation
-
Confirm VRML import is enabled in your applicationCheck application settings, configuration files, or plugin directories for VRML-related modules, or inspect which OCCT modules are loaded at runtimeAffected if VRML file import or VrmlData modules are loaded or enabled in applications using this OCCT installation
-
Determine if untrusted VRML files are processedReview application logs, file access patterns, or user workflows for evidence of VRML file parsing; check if applications accept VRML input from external sourcesAffected if Applications using this OCCT installation parse VRML files, especially from untrusted or external sources
You are affected if Open CASCADE Technology version <= 7.9.3 or = 8.0.0 is installed AND your applications load the VRML parser library (libTKDEVRML.so) to process VRML files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataAvoid opening untrusted or unvalidated VRML files with applications using OCCT. Implement file validation and sandboxing before parsing. Apply any vendor patches when available.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42478 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-42478 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data