CVE-2026-7454
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 · uneditedA maliciously crafted WRL file, when parsed through Autodesk 3ds Max, can force a Memory Corruption vulnerability. A malicious actor can leverage this vulnerability to execute arbitrary code in the context of the current process.
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 · moderate confidenceA memory corruption vulnerability exists in Autodesk 3ds Max when parsing maliciously crafted WRL (VRML) files. The vulnerability allows an attacker to execute arbitrary code in the context of the current process by triggering improper memory handling during file parsing.
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= 2026= 2027CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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.
-
Verify 3ds Max installationCheck for Autodesk 3ds Max installation in Program Files or via installed programs list (Windows: Add/Remove Programs, macOS: Applications folder or Launchpad)Affected if 3ds Max 2026 or 2027 is installed on the system
-
Confirm installed version numberOpen 3ds Max and go to Help > About Autodesk 3ds Max, or check the executable properties (right-click 3dsmax.exe > Properties > Details) for the Product versionAffected if Version shows 2026 or 2027 (exact match to affected versions)
-
Check WRL file handler registrationOn Windows: Search for .wrl file extension associations in Registry under HKCR\.wrl or check default programs settings. On macOS: right-click any .wrl file and select Get Info to see what application opens itAffected if 3ds Max is registered as the default handler for .wrl files or is one of the associated applications
-
Inspect recent WRL file accessReview recent file access logs, browser download histories, or email attachments that may contain WRL files. Check Windows Event Viewer Security/Application logs or File Explorer Recent Items for .wrl file interactionsAffected if User has recently opened or accessed WRL files from untrusted sources in 3ds Max
-
Detect WRL import module presenceCheck the 3ds Max plug-in directory (typically in the installation folder under plugins or stdplugs) for WRL import related DLLs or modulesAffected if WRL import functionality is present and enabled in the 3ds Max installation
The environment is affected if 3ds Max versions 2026 or 2027 are installed and WRL file handling is enabled or has been used to open 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 dataApply the vendor-supplied patch from Autodesk when available. Until then, restrict opening WRL files from untrusted sources and consider sandboxing or network isolation for systems running 3ds Max.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7454 — 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-7454 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