Skip to main content

Autodesk 3ds Max CVE-2026-7452

| EUVDEUVD-2026-31911 HIGH
Classic Buffer Overflow (CWE-120)
2026-05-26 autodesk GHSA-86fj-8658-phwx
7.8
CVSS 3.1 · Vendor: autodesk
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Craft malicious WRL file
  2. Delivery
    Deliver via email or asset marketplace
  3. Exploit
    Victim imports file into 3ds Max
  4. Install
    WRL parser overflows buffer (CWE-120)
  5. C2
    Hijack control flow in 3ds Max process
  6. Execute
    Execute arbitrary code as current user
  7. Impact
    Steal assets or pivot internally

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Buffer copy size validation
MITRE ATT&CK

1 technique across 1 tactic: Execution

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 user of Autodesk 3ds Max 2026 (<2026.1) or 3ds Max 2027 (<2027.1) on a workstation to open or import an attacker-supplied WRL (VRML) file through the 3ds Max WRL/VRML import path - the vulnerable code is the WRL file parser, so any workflow that does not ingest .wrl files is not exposed. Limiting factors: CVSS UI:R confirms user interaction is mandatory (the file must be opened/imported, not merely present on disk); AV:L means there is no remote network reachability - the file must arrive via email, download, shared storage, or asset pipeline; PR:N means the attacker needs no prior credentials on the target host but the resulting code runs only at the victim user's privilege level (S:U, no scope change); and only the two named 2026/2027 release lines are listed as affected, so earlier supported releases and the already-patched .1 builds are out of scope based on the data provided.

Impact

The CVSS vector AV:L/AC:L/PR:N/UI:R paints this as a local, user-interaction-driven client-side bug - the 'local' vector reflects that the attacker delivers a file the victim must open rather than reaching the product over a network. Confidentiality, integrity, and availability impacts are all High, and SSVC agrees the technical impact is 'total,' but SSVC also marks Exploitation as 'none' and Automatable as 'no,' and EPSS sits at 0.01% (0th percentile), so this is not currently a mass-exploitation threat. It is not on CISA KEV and no public PoC is identified. Realistic risk is moderate and concentrated on organizations that routinely ingest third-party 3D assets (VFX studios, game studios, architectural/engineering firms, marketplaces) where booby-trapped WRL files can plausibly reach designers via email, asset packs, or supply-chain content; for shops that never touch WRL content the practical risk is low. No conflicting signals were observed in the provided data.

Exploit ScenarioDerived

An attacker emails or hosts a malicious .wrl asset (for example, posing as a free VRML model on a 3D asset marketplace or as a vendor deliverable to a VFX artist) and convinces the victim to open or import it into 3ds Max. When the WRL parser processes the crafted geometry/strings, the buffer overflow corrupts memory and the attacker's shellcode executes as the logged-in designer, enabling credential theft, lateral movement, or tampering with production assets. No public exploit is identified at time of analysis, so an attacker would need to develop the exploit themselves.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 08, 2026

Arbitrary code execution in Autodesk 3ds Max 2026 (<2026.1) and 2027 (<2027.1) is possible when a user opens a maliciously crafted WRL (VRML) file, triggering a memory corruption (buffer overflow) condition that runs attacker code in the context of the 3ds Max process. The flaw was reported by Autodesk itself and carries a CVSS 7.8 (local, user-interaction required); no public exploit has been identified and EPSS is 0.01%, indicating no observed exploitation activity to date. SSVC rates technical impact as total but exploitation as none and not automatable, consistent with a file-format parser bug requiring social engineering.

RemediationAI

Vendor-released patches are available: upgrade Autodesk 3ds Max 2026 to 2026.1 or later, and Autodesk 3ds Max 2027 to 2027.1 or later, delivered via Autodesk Access (https://www.autodesk.com/products/autodesk-access/overview) as referenced in advisory ADSK-SA-2026-0006 (https://www.autodesk.com/trust/security-advisories/adsk-sa-2026-0006). Until patching is completed, compensating controls include refusing to open WRL/VRML files from untrusted or unverified sources, stripping or blocking .wrl attachments at the email gateway, and disallowing WRL imports in shared asset pipelines - the trade-off is loss of legitimate VRML interchange, which is uncommon in modern workflows. Running 3ds Max as a standard (non-administrative) user limits post-exploitation blast radius but does not prevent code execution in the user's session, and opening suspect files inside a disposable VM or sandboxed workstation isolates impact at the cost of workflow friction.

Affected VersionsENISA

3ds Max 2026 <2026.1
3ds Max 2027 <2027.1

Affected Packages

euvd 3ds_max fix: 2026.1, 2027.1

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

3ds Max is a Windows-based 3D modeling and animation suite that imports a wide range of legacy and interchange formats, including WRL (VRML 2.0 / Virtual Reality Modeling Language) scene files. The vulnerability resides in the WRL parser, which fails to safely bound user-controlled data while reading the file - the root cause class CWE-120 (Classic Buffer Overflow / 'Buffer Copy without Checking Size of Input') indicates that attacker-controlled length or content from the WRL stream is copied into a fixed-size buffer, corrupting adjacent memory. Because parsing happens in-process, successful corruption yields control flow hijack in the 3ds Max process, which typically runs at the interactive user's privilege level on Windows workstations (cpe:2.3:a:autodesk:3ds_max).

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

Vendor (autodesk) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Primary rating from Vendor (autodesk) · only source for this CVE.

CVSS VectorVendor: autodesk

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

A maliciously crafted WRL 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

Why It Matters

Design organizations using Autodesk 3ds Max 2026 or 2027 face a critical risk when users open malicious model files that execute arbitrary code on workstations and compromise intellectual property. Per current threat intelligence, no public exploit identified at time of analysis, but the combination of 3ds Max's widespread use and the severity of unrestricted code execution make this a priority vulnerability. Patching to versions 2026.1 and 2027.1 within 7 days will restore baseline security and protect sensitive design assets.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.0%
Top 100% exploitable
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

CVE-2026-0538 HIGH
8.4 Feb 04

Arbitrary code execution in Autodesk 3ds Max occurs when the application parses a maliciously crafted GIF file, triggeri

CVE-2026-0661 HIGH
8.4 Feb 04

Arbitrary code execution in Autodesk 3ds Max occurs when the application parses a maliciously crafted RGB image file, re

CVE-2026-0537 HIGH
8.4 Feb 04

Arbitrary code execution in Autodesk 3ds Max occurs when the application parses a maliciously crafted RGB image file, tr

CVE-2026-0660 HIGH
8.4 Feb 04

Stack-based buffer overflow in Autodesk 3ds Max enables arbitrary code execution when the application parses a malicious

CVE-2026-16782 HIGH
7.8 Aug 24

Out-of-bounds read in Autodesk 3ds Max's SVG file parser enables crash, sensitive memory disclosure, or arbitrary code e

CVE-2026-7455 HIGH
7.8 Aug 24

Out-of-bounds write in Autodesk 3ds Max's FLT file parser allows an attacker to cause a crash, corrupt data, or execute

CVE-2026-19568 HIGH
7.8 Aug 24

Memory corruption via maliciously crafted SVG files in Autodesk 3ds Max allows arbitrary code execution within the curre

CVE-2026-16783 HIGH
7.8 Aug 24

Out-of-bounds write in Autodesk 3ds Max's Alembic (ABC) file parser enables arbitrary code execution in the context of t

CVE-2025-11797 HIGH
7.8 Nov 12

A maliciously crafted DWG file, when parsed through Autodesk 3ds Max, can force a Use-After-Free vulnerability. Rated hi

CVE-2025-11795 HIGH
7.8 Nov 12

A maliciously crafted JPG file, when parsed through Autodesk 3ds Max, can force an Out-of-Bounds Write vulnerability. Ra

CVE-2026-7454 HIGH
7.8 May 26

Arbitrary code execution in Autodesk 3ds Max 2026 and 2027 occurs when the application parses a maliciously crafted WRL

CVE-2026-0662 HIGH
7.8 Feb 04

Arbitrary code execution in Autodesk 3ds Max occurs when users open max files from maliciously crafted project directori

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy