Code execution via crafted WRL file parsing
Published May 26, 2026 · Updated May 26, 2026
Memory corruption in Autodesk 3ds Max 2026 before 2026.1 and 2027 before 2027.1 allows attackers to execute code via a crafted WRL file. Autodesk identifies the WRL parser as the affected locus but has not published the specific memory operation or input field that triggers corruption. Exploitation requires user interaction to parse the file, and successful code runs with the privileges of the current 3ds Max process.
Summary
What happened
Memory corruption in Autodesk 3ds Max 2026 before 2026.1 and 2027 before 2027.1 allows attackers to execute code via a crafted WRL file. Autodesk identifies the WRL parser as the affected locus but has not published the specific memory operation or input field that triggers corruption. Exploitation requires user interaction to parse the file, and successful code runs with the privileges of the current 3ds Max process.
The record
- CVE
- CVE-2026-7452
- Published
- May 26, 2026
- Updated
- May 26, 2026
- Vendor
- Autodesk
- Product
- 3ds Max
- Classifications
- CWE-120, T1204.002, T1203
- 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.
Weakness, pattern, technique
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