CVE-2026-7453: WRL File Parsing Memory Exhaustion in Autodesk 3ds Max
A maliciously crafted WRL file, when parsed through Autodesk 3ds Max, can cause a Stack Exhaustion vulnerability, leading to a denial-of-service condition.
Security readout for executives and security teams
Plain-English summary
A malicious WRL file can crash Autodesk 3ds Max by exhausting stack memory during parsing. This is a denial-of-service issue, not a data theft or code execution issue based on the provided sources. The business risk is interrupted creative or engineering workstations when users open crafted files.
Executive priority
Treat this as a moderate operational resilience issue for teams dependent on 3ds Max. It should not outrank remotely exploitable or data-compromise vulnerabilities, but affected creative and engineering workstations should be updated and protected from untrusted WRL files.
Technical view
CVE-2026-7453 is a CWE-674 uncontrolled recursion issue in Autodesk 3ds Max WRL parsing. It affects 3ds Max 2026 and 2027. CVSS 3.1 is 5.5 with local attack vector, low complexity, no privileges, required user interaction, unchanged scope, and high availability impact only.
Likely exposure
Exposure is most likely on workstations running Autodesk 3ds Max 2026 or 2027 where users import or open WRL files, especially files received from external parties. The bundle lists other versions as unaffected by default, but organizations should verify against Autodesk guidance.
Exploitation context
The source bundle does not indicate active exploitation, and KEV status is false. Exploitation requires a user to open or parse a maliciously crafted WRL file locally in Autodesk 3ds Max. The known impact is application denial of service.
Researcher notes
Evidence supports denial of service through stack exhaustion only. Do not assume code execution, broader Autodesk product impact, or active exploitation from this bundle. The most useful validation is version exposure, WRL workflow presence, and vendor update status.
Mitigation direction
Check Autodesk advisory ADSK-SA-2026-0006 for product-specific update guidance.
Use Autodesk Access to identify and apply relevant Autodesk updates.
Limit opening WRL files from untrusted or unauthenticated sources.
Prioritize 3ds Max 2026 and 2027 systems for review.
Use standard endpoint controls to quarantine suspicious project files.
Validation and detection
Inventory endpoints for Autodesk 3ds Max 2026 and 2027 installations.
Confirm installed build and update status against Autodesk guidance.
Identify teams that import WRL files from external sources.
Review recent 3ds Max crash reports involving WRL file handling.
Document compensating controls where updates cannot be applied quickly.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-674: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-674 · source CWE mapping
Uncontrolled Recursion
Uncontrolled Recursion represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.