Autodesk 3ds Max
CVE-2026-0661
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted RGB file to artist
-
DeliveryArtist opens or imports texture in 3ds Max
-
ExploitRGB parser performs out-of-bounds write
-
ExecutionHijack control flow in 3ds Max process
-
PersistExecute arbitrary code as artist user
-
ImpactExfiltrate project assets or pivot into studio network
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2021 - Vulnerable and Outdated Components
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a victim running Autodesk 3ds Max to load or import a specifically crafted RGB (SGI image format) file using the application's native RGB parser; the attacker must deliver that file to the local workstation, since the CVSS attack vector is Local (AV:L). Limiting factors are that the victim must actually open the malicious asset in 3ds Max (despite UI:N in the published vector, the description requires the file be 'parsed through' 3ds Max), the target must have an unpatched 3ds Max build per ADSK-SA-2026-0002, and impact is bounded to the privileges of the user account running the application - so non-admin artists cannot be escalated to SYSTEM through this bug alone. No authentication to 3ds Max or the OS beyond the artist's own session is required (PR:N). |
| Impact | The CVSS vector AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H scores 8.4 and tells a consistent story with the description: exploitation requires the file to reach the local 3ds Max process (AV:L) but no privileges and, per the vector, no user interaction once the file is reached - though in practice an artist must still open or import the RGB asset, which is a meaningful real-world limiter. EPSS is extremely low at 0.01% (1st percentile) and there is no public exploit identified and no CISA KEV listing, so this is not a mass-exploitation risk; it is a targeted, social-engineering-dependent client-side bug, most relevant to studios that ingest 3D assets from untrusted sources or marketplaces. Note the apparent tension between UI:N in the CVSS vector and a description that clearly implies a user opening a file - UI:N here likely reflects Autodesk's scoring choice rather than a true zero-click vector, and defenders should treat this as user-interaction-dependent. |
| Exploit ScenarioDerived | An attacker emails a 3D artist a 'reference texture pack' containing a maliciously crafted .rgb file, or seeds it on a community asset marketplace; when the artist imports the texture into a 3ds Max scene, the out-of-bounds write fires and the attacker gains code execution as the artist, allowing theft of project files, render-farm credentials, or pivoting into the studio network. No public exploit code is identified at time of analysis, so any campaign would require the attacker to develop the memory-corruption payload from the patch diff or independent research. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv3 – Jun 03, 2026
Arbitrary code execution in Autodesk 3ds Max occurs when the application parses a maliciously crafted RGB image file, resulting in a CWE-787 out-of-bounds write that corrupts memory and lets an attacker run code in the context of the user running 3ds Max. No public exploit identified at time of analysis, and the EPSS probability is only 0.01%, but the CVSS base score of 8.4 reflects the high impact when a victim is convinced to open a weaponized asset file.
Earlier versions of this analysis (2)
Arbitrary code execution in Autodesk 3ds Max occurs when the application parses a maliciously crafted RGB image file, triggering a memory corruption condition (CWE-787 out-of-bounds write). Successful exploitation allows an attacker to run code in the context of the current 3ds Max process on the victim's workstation. No public exploit identified at time of analysis, and EPSS exploitation probability is very low (0.01%, 1st percentile), though the high CVSS of 8.4 reflects significant impact if a user is convinced to open a malicious file.
A maliciously crafted RGB file, when parsed through Autodesk 3ds Max, can force a Memory Corruption vulnerability. A malicious actor can leverage this vulnerability to execute arbitrary code in the context of the current process. [CVSS 7.8 HIGH]
RemediationAI
Apply the fixed 3ds Max build identified in Autodesk security advisory ADSK-SA-2026-0002 (https://www.autodesk.com/trust/security-advisories/adsk-sa-2026-0002); exact patched version numbers are listed in that advisory and should be deployed through Autodesk Access. Until the patched build is rolled out, restrict 3ds Max workstations from opening RGB files from untrusted or external sources - block .rgb (and the related .sgi/.bw/.rgba variants) at email gateways and asset-ingest pipelines, require that third-party textures be converted to PNG or TIFF by an isolated conversion service before they reach artist workstations, and run 3ds Max under a non-administrator account so that successful exploitation is contained to the user's profile. The trade-off is that converting or blocking RGB files breaks legitimate workflows that consume SGI-format textures from vendors or legacy archives, so coordinate the block with asset-management teams.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Autodesk 3ds Max is a Windows-based 3D modeling, animation, and rendering suite (CPE cpe:2.3:a:autodesk:3ds_max) that natively imports a wide range of legacy image formats, including the SGI RGB raster format historically used as texture input. The root cause is classified as CWE-787 (Out-of-bounds Write), meaning the RGB parser fails to correctly validate length, offset, or channel fields in the file header or pixel stream and writes attacker-controlled bytes past the bounds of a heap or stack buffer. Because image parsing happens in-process inside the main 3ds Max executable, corruption directly affects the running application's memory and control flow, enabling code execution under the user's security context.
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:N/S:U/C:H/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionCVE.org
A maliciously crafted RGB file, when parsed through Autodesk 3ds Max, can force a Memory Corruption vulnerability. A malicious actor can leverage this vulnerability to execute arbitrary code in the context of the current process.
Executive ViewAI
Autodesk 3ds Max contains a high-severity vulnerability (CVE-2026-0661, CVSS 8.4) that allows arbitrary code execution when users open maliciously crafted RGB image files, affecting any employee using the application. No public exploit identified at time of analysis, though exploitation requires only a user opening a file, creating significant risk across the organization.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict 3ds Max access to trained, authorized personnel; (2) Implement file-level controls blocking RGB file access from untrusted sources (removable media, external downloads, unverified suppliers); (3) Run 3ds Max in sandboxed or isolated environments where feasible; (4) Monitor endpoint logs for abnormal child process creation or memory corruption indicators; (5) Establish vendor notification workflow to apply patches immediately upon release.
Threat Intelligence Overview
NVD
CVE.org
EPSS
VulDB
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.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Affected Products (CPE)CVE.org
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, 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
Arbitrary code execution in Autodesk 3ds Max 2026 (<2026.1) and 2027 (<2027.1) is possible when a user opens a malicious
GitHub PoC
Exploit-DB