Denial of service via uncontrolled WRL recursion
Published May 26, 2026 · Updated May 26, 2026
Stack exhaustion in WRL parsing in Autodesk 3ds Max 2026 and 2027 allows attackers to crash the application with a crafted file. Autodesk identifies uncontrolled recursion and stack exhaustion but has not disclosed the affected parser routine or malformed WRL structure. A user must open the crafted file; the reported consequence is denial of service, with no published confidentiality or integrity impact.
Summary
What happened
Stack exhaustion in WRL parsing in Autodesk 3ds Max 2026 and 2027 allows attackers to crash the application with a crafted file. Autodesk identifies uncontrolled recursion and stack exhaustion but has not disclosed the affected parser routine or malformed WRL structure. A user must open the crafted file; the reported consequence is denial of service, with no published confidentiality or integrity impact.
The record
- CVE
- CVE-2026-7453
- Published
- May 26, 2026
- Updated
- May 26, 2026
- Vendor
- Autodesk
- Product
- 3ds Max
- Classifications
- CWE-674, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 2026CVE publishedPublication date reported by the CVE source.
- May 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2026 <2026.1
- Affected versionversion=2027 <2027.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo