dbcve.org
3ds MaxApplication · Autodesk

CVE-2026-7453

MEDIUM · 5.5 CVSS v3.1 Published 2026-05-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
A maliciously crafted WRL file, when parsed through Autodesk 3ds Max, can cause a Stack Exhaustion vulnerability, leading to a denial-of-service condition.

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 confidence

A stack exhaustion vulnerability exists in Autodesk 3ds Max's WRL (VRML) file parser. When a specially crafted WRL file with deeply nested structures is opened, it causes excessive stack consumption, leading to application crash or unresponsiveness (denial of service).

MitigationAvoid opening WRL files from untrusted sources. Implement file size and complexity limits where possible, and monitor for patches from Autodesk.

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
3ds MaxApplication
Affected:= 2026= 2027

CVSS 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed 3ds Max version
    Open 3ds Max, go to Help menu and select 'About 3ds Max' to view the exact version number, or right-click the 3dsmax.exe executable file and select Properties > Details to see the Product Version
    Affected if The version shown is 2026 or 2027
  2. Confirm WRL file import capability exists
    In 3ds Max, go to File > Import and check if 'VRML (*.wrl;*.wrz)' or 'WRL' appears in the file type dropdown list, or look for WRL-related import options in the asset tracking or scene explorer
    Affected if WRL file import option is present and accessible in the application
  3. Verify WRL files have been opened recently
    Check recent files list (File > Recent Files) or search the user documents and project folders for .wrl files that may have been imported, or check the 3ds Max script listener log for import activity
    Affected if WRL files have been opened or imported into the current or recent projects

You are affected if you run Autodesk 3ds Max version 2026 or 2027 and use the software to open or import WRL/VRML files, as the stack exhaustion occurs during parsing of maliciously crafted WRL files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Avoid opening WRL files from untrusted sources. Implement file size and complexity limits where possible, and monitor for patches from Autodesk.

Fix this in 3ds Max Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7453 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7453 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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