Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious WRL file with deep recursive VRML nodes
-
DeliveryDeliver file to target via phishing or asset repository
-
ExploitUser opens file in affected 3ds Max version
-
ExecutionRecursive parser descends without depth limit
-
PersistCall stack exhausted
-
ImpactApplication crashes (DoS)
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Recursion depth limits
|
| Exploitation Conditions | Exploitation requires that a local user manually open a maliciously crafted WRL file within an affected version of Autodesk 3ds Max - this is confirmed by AV:L (local attack vector) and UI:R (user interaction required) in the CVSS vector. The WRL/VRML import functionality must be accessible and enabled within 3ds Max; disabling or removing this import path would prevent exploitation. The vulnerability is version-scoped to 3ds Max 2026 prior to 2026.1 and 2027 prior to 2027.1 - patched or out-of-range versions are not affected. There is no network-facing component and no remote trigger mechanism; the attack cannot be initiated without the target user actively opening the file. The attack is not automatable per SSVC assessment. Impact is strictly limited to an application-level crash - code execution, privilege escalation, and data exfiltration are not possible outcomes of this vulnerability. |
| Impact | The CVSS 3.1 vector AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H reflects a local, file-triggered attack requiring user interaction, with impact strictly limited to availability - no confidentiality or integrity compromise is possible. The score of 5.5 (Medium) is appropriate and does not understate risk. EPSS at 0.00% in the 0th percentile is a strong signal that this vulnerability class and product combination are effectively unexploited at time of analysis. The SSVC assessment reinforces this: exploitation status is none, the attack is not automatable (manual social engineering required), and technical impact is only partial. KEV status is not confirmed. One data conflict worth flagging: the intelligence tags include 'Information Disclosure,' which directly contradicts the CVSS impact scores showing C:N - no confidentiality impact is indicated anywhere else in the dataset. This tag appears to be a metadata classification error and should not inform risk decisions. Net assessment: this is a real but low-priority vulnerability suitable for standard patching cycles, not emergency response. |
| Exploit ScenarioDerived | An attacker crafts a WRL file containing deeply nested or cyclically referencing VRML node structures specifically designed to cause unbounded recursion in 3ds Max's parser. The file is delivered to a target 3D artist or designer via a phishing email, compromised asset repository, or malicious download link - social engineering is required since the victim must manually open the file in 3ds Max. Upon opening, the recursive parser exhausts the call stack, immediately crashing the application and destroying any unsaved work, constituting a denial-of-service. No public exploit code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 08, 2026
Stack exhaustion in Autodesk 3ds Max 2026 and 2027 can be triggered by opening a maliciously crafted WRL (VRML) file, causing an application crash and denial-of-service condition for the affected user. Exploitation requires local access and deliberate user interaction - a victim must be socially engineered into opening the weaponized file. No active exploitation is identified; EPSS sits at 0.00% and SSVC exploitation status is confirmed none, placing real-world risk well below what the moderate CVSS score of 5.5 might initially suggest.
RemediationAI
Upgrade to Autodesk 3ds Max 2026.1 or 2027.1, which contain the vendor-released patch per Autodesk Security Advisory ADSK-SA-2026-0006 (https://www.autodesk.com/trust/security-advisories/adsk-sa-2026-0006). Updates can be obtained through the Autodesk Access utility at https://www.autodesk.com/products/autodesk-access/overview. For organizations unable to patch immediately, a practical compensating control is to instruct users not to open WRL files from untrusted or unverified sources, as the exploit path is entirely dependent on user-initiated file opening. If 3ds Max application settings allow disabling or restricting the VRML/WRL import feature, doing so would eliminate the attack surface at the cost of removing that import capability from legitimate workflows. No additional network-layer controls are applicable given the local-only attack vector.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
WRL files use the VRML (Virtual Reality Modeling Language) format, a structured 3D scene description language supported in 3ds Max as an import format. CWE-674 (Uncontrolled Recursion) identifies the root cause: the WRL parser fails to enforce a maximum recursion depth when traversing deeply nested or self-referencing node structures within the file, causing the call stack to grow unboundedly until it is exhausted. This is a classic parser-level vulnerability where input is not validated for structural depth before recursive descent begins. The CPE identifier cpe:2.3:a:autodesk:3ds_max:*:*:*:*:*:*:*:* applies across all platform builds of 3ds Max, and ENISA EUVD data (EUVD-2026-31914) narrows the scope to the 2026 and 2027 release trains specifically. The vulnerability is entirely within the file-parsing subsystem and carries no network-facing attack surface.
Know when 3ds Max gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Primary rating from Vendor (autodesk) · only source for this CVE.
CVSS VectorVendor: autodesk
Lifecycle Timeline
1DescriptionCVE.org
A maliciously crafted WRL file, when parsed through Autodesk 3ds Max, can cause a Stack Exhaustion vulnerability, leading to a denial-of-service condition.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Arbitrary code execution in Autodesk 3ds Max occurs when the application parses a maliciously crafted GIF file, triggeri
Arbitrary code execution in Autodesk 3ds Max occurs when the application parses a maliciously crafted RGB image file, re
Arbitrary code execution in Autodesk 3ds Max occurs when the application parses a maliciously crafted RGB image file, tr
Stack-based buffer overflow in Autodesk 3ds Max enables arbitrary code execution when the application parses a malicious
Out-of-bounds read in Autodesk 3ds Max's SVG file parser enables crash, sensitive memory disclosure, or arbitrary code e
Out-of-bounds write in Autodesk 3ds Max's FLT file parser allows an attacker to cause a crash, corrupt data, or execute
Memory corruption via maliciously crafted SVG files in Autodesk 3ds Max allows arbitrary code execution within the curre
Out-of-bounds write in Autodesk 3ds Max's Alembic (ABC) file parser enables arbitrary code execution in the context of t
A maliciously crafted DWG file, when parsed through Autodesk 3ds Max, can force a Use-After-Free vulnerability. Rated hi
A maliciously crafted JPG file, when parsed through Autodesk 3ds Max, can force an Out-of-Bounds Write vulnerability. Ra
Arbitrary code execution in Autodesk 3ds Max 2026 and 2027 occurs when the application parses a maliciously crafted WRL
Arbitrary code execution in Autodesk 3ds Max occurs when users open max files from maliciously crafted project directori
EUVD-2026-31914
GHSA-jxh4-3xvg-j3fm
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB