Autodesk 3ds Max EUVD-2026-31915

Exploitation requires the victim to open an attacker-supplied WRL (VRML) file in a vulnerable installation of Autodesk 3ds Max 2026 (<2026.1) or 3ds Max 2027 (<2027.1); per CVSS UI:R the attack cannot succeed without that user action, and per AV:L the malicious file must reach the local system (e.g., via email, download, or shared storage) rather than being delivered over a network listener. No authentication to 3ds Max or to the workstation is required of the attacker (PR:N), and no special non-default configuration is needed - the vulnerable WRL import path is part of standard 3ds Max functionality. Exploitation is bounded to the privileges of the user running 3ds Max (S:U), so impact on the broader host depends on whether that user is a local administrator.

Risk signals are largely consistent and point to a serious but bounded threat. CVSS 7.8 (AV:L/AC:L/PR:N/UI:R/C:H/I:H/A:H) describes a local attack vector requiring user interaction - the victim must open the malicious WRL file - yielding full confidentiality, integrity, and availability impact within the user's process scope. EPSS at 0.01% (3rd percentile) and SSVC 'Exploitation: none, Automatable: no' both indicate no observed in-the-wild activity and no scalable exploitation path, while SSVC 'Technical Impact: total' confirms that when exploitation succeeds the attacker fully controls the process. There is no CISA KEV listing and no public exploit identified at time of analysis. The realistic priority is moderate: high impact per successful exploit but dependent on social engineering and targeted file delivery to 3ds Max users (typically VFX, architecture, and game-studio workstations), not mass scanning.

An attacker crafts a malicious WRL scene file and delivers it to a 3ds Max user via spear-phishing, a compromised asset library, or a shared project drive, framing it as a model or scene to review. When the artist opens the file in 3ds Max 2026 or 2027, the buffer overflow in the WRL parser triggers and executes shellcode in the user's process, giving the attacker code execution on the workstation with the artist's privileges. No public exploit has been identified at time of analysis, but the bug class (classic buffer overflow in a parser) is well within reach of a skilled exploit developer.