EUVD-2026-65150
GHSA-25qw-x66x-j232
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious SVG file
-
DeliveryDeliver to target via phishing or shared asset folder
-
ExploitVictim opens file in 3ds Max
-
ExecutionSVG parser triggers out-of-bounds read
-
ImpactRead process memory or gain code execution
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The victim must actively open a maliciously crafted SVG file using an unpatched version of Autodesk 3ds Max (2026 prior to 2026.3.4 or 2027 prior to 2027.2.0) on a local workstation. User interaction is required (UI:R per CVSS); the attack is not remotely triggerable without the victim's action. No elevated privileges are required to trigger the vulnerability (PR:N), but the attack surface is limited to machines with 3ds Max installed - narrowing the affected population to design, architecture, VFX, and game development workstations. Exploitation is limited by: (1) the requirement that the SVG file be delivered to and opened on the target system, (2) SSVC automatable status of 'no' precluding mass-scanning attacks, and (3) scope unchanged (S:U), meaning the exploit cannot directly pivot to other system processes or elevated contexts. |
| Impact | CVSS 7.8 High reflects a worst-case scenario (full C/I/A) but the local attack vector (AV:L) and mandatory user interaction (UI:R) impose meaningful friction: an attacker must deliver the crafted SVG to the target machine and engineer the victim into opening it in 3ds Max. EPSS at 0.25% (16th percentile) is low, and SSVC corroborates this with exploitation status 'none' and automatable 'no,' meaning mass exploitation pipelines are not currently viable. Notably, SSVC rates technical impact as 'partial' rather than 'total,' which tempers the CVSS-implied severity; this may reflect the constrained process-context scope (S:U, unchanged scope) and the social-engineering prerequisite. No conflict exists between CVSS AV:L and the description - SVG is opened locally within the application, not via a network service. The primary threat model is spear-phishing or supply-chain file delivery targeting architects, VFX artists, and game developers who routinely exchange 3ds Max asset files. Patch availability from the vendor and the non-automated attack surface collectively push real-world urgency below the raw CVSS headline. |
| Exploit ScenarioDerived | An attacker targeting a 3D artist or architect sends a weaponized SVG embedded in a project asset archive or shared collaboration folder. When the victim opens the file in unpatched 3ds Max 2026 or 2027, the SVG parser reads out of bounds, either leaking process memory (credentials, scene data) or, under a more sophisticated heap-shaping attack, redirecting execution to attacker-controlled shellcode. No public proof-of-concept code has been identified at time of analysis, making this scenario currently theoretical but technically plausible given the CWE-125/RCE classification. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Aug 28, 2026
Out-of-bounds read in Autodesk 3ds Max's SVG file parser enables crash, sensitive memory disclosure, or arbitrary code execution within the 3ds Max process context when a user opens a maliciously crafted SVG file. Affected releases span 3ds Max 2026 prior to 2026.3.4 and 3ds Max 2027 prior to 2027.2.0, as confirmed by EUVD-2026-65150. EPSS stands at 0.25% (16th percentile) with SSVC exploitation status of 'none,' indicating no current active exploitation; however, the RCE-capable impact triad warrants patching in affected professional environments.
Earlier versions of this analysis (1)
Out-of-bounds read in Autodesk 3ds Max's SVG file parser allows an attacker who delivers a crafted SVG to cause application crashes, disclose sensitive process memory, or potentially execute arbitrary code within the 3ds Max process context. The attack requires a user to open the malicious file, making social engineering the primary delivery vector in professional design and VFX environments where externally sourced asset files are routine. No public exploit code has been identified and the vulnerability does not appear in the CISA KEV catalog at time of analysis, though the vendor-stated RCE potential warrants prioritization above the published CVSS 5.3 score suggests.
RemediationAI
Upgrade to Autodesk 3ds Max 2026.3.4 or later (for the 2026 release line) or to 2027.2.0 or later (for the 2027 release line), per the vendor advisory at https://www.autodesk.com/trust/security-advisories/adsk-sa-2026-0014. Autodesk Access (https://www.autodesk.com/products/autodesk-access/overview) can be used to apply updates. If immediate patching is not feasible, a targeted compensating control is to restrict SVG file ingestion: configure OS-level file association policies to prevent 3ds Max from being the default handler for SVG files, and instruct users to avoid opening SVG assets from untrusted sources. Note that this workaround does not prevent exploitation if a user manually imports an SVG through 3ds Max's internal asset pipeline. No patch version beyond the confirmed fix versions above has been independently verified from the available data.
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
The root cause is CWE-125 (Out-of-Bounds Read) in Autodesk 3ds Max's SVG parsing subsystem. SVG (Scalable Vector Graphics) is an XML-based vector image format; parsers that fail to validate element dimensions, path lengths, or embedded data offsets can read past allocated buffer boundaries. CWE-125 typically manifests as a memory disclosure primitive that, under controlled heap layout conditions, can be escalated to RCE - consistent with the reported crash/read/execute impact triad. CPE data (cpe:2.3:a:autodesk:3ds_max:*:*:*:*:*:*:*:*) confirms this affects the 3ds Max desktop application directly. EUVD-2026-65150 narrows affected version ranges to 3ds Max 2026.0.0 through 2026.3.4 (exclusive) and 2027.0.0 through 2027.2.0 (exclusive). The vulnerability was reported by Autodesk PSIRT, indicating internal or coordinated external discovery.
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:H/I:H/A:H
File parsed locally with no privileges needed, but user must open it; full C/I/A justified by RCE-capable OOB read within process context.
Primary rating from Vendor (autodesk).
CVSS VectorNVD
Lifecycle Timeline
3DescriptionNVD
A maliciously crafted SVG file, when parsed through Autodesk 3ds Max, can force an Out-of-Bounds Read vulnerability. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.
Executive ViewAI
Autodesk 3ds Max versions 2026 (prior to 2026.3.4) and 2027 (prior to 2027.2.0) contain a critical parser vulnerability enabling remote code execution when users open maliciously crafted SVG files. No active exploitation has been observed to date, but organizations using 3ds Max for design and content creation should prioritize patching to eliminate the risk of system compromise.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
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
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
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 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
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
Arbitrary code execution in Autodesk 3ds Max 2026 (<2026.1) and 2027 (<2027.1) is possible when a user opens a malicious
Out-of-bounds write in Autodesk 3ds Max 2026 and 2027 enables arbitrary code execution when a user opens a maliciously c
Autodesk 3ds Max is vulnerable to arbitrary code execution when processing maliciously crafted GIF files due to a stack-
Exploit-DB