CVE-2026-126825: Autodesk 3ds Max · Out-of-bounds Read
Affects Autodesk 3ds MaxSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium : upgrade to 2027.3.0 when convenient.
Data as of 19 Nov 2026, 14:22 UTC
Thin evidence
One scorer or none| CNA (autodesk) | CVSS 3.1 | 5.5 |
|---|
- Patch
- Available – fixed in 2027.3.0
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade Autodesk 3ds Max to 2027.3.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Autodesk3ds Max | Affected
| Fixed in
|
CPE configurations (1)
cpe:2.3:a:autodesk:3ds_max:2027:*:*:*:*:*:*:*
AI-suggested
Upgrade Autodesk 3ds Max to version 2027.3.0 or later, where this vulnerability is fixed. If you cannot patch yet, avoid importing or loading untrusted SBSAR files via the Substance plugin. No other vendor mitigation or workaround is indicated.
Description
CVE-2026-126825 is an out-of-bounds read vulnerability in Autodesk 3ds Max 2027 versions from 2027.0.0 up to but not including 2027.3.0. It occurs when a maliciously crafted SBSAR file is imported or loaded via the Substance in 3ds Max plugin. Exploitation can cause the application to crash or potentially allow reading of sensitive process memory. The vulnerability has a medium severity with a CVSS score of 5.5. Autodesk fixed this issue in version 2027.3.0.