Quick answers
- Is CVE-2026-0537 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-0537 being exploited in the wild.
- How severe is CVE-2026-0537?
- High severity, with a CVSS score of 8.4, published 4 February 2026.
- Which products and versions are affected?
- Autodesk 3ds Max 2026 before 2026.3.2.
- Is there a fix for CVE-2026-0537?
- A patch was published on 2026-02-06: NIST analysis indicates fix in 2026.3.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-0537 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-0537?
- Check whether you run Autodesk 3ds Max at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A memory corruption vulnerability exists in Autodesk 3ds Max due to an out-of-bounds write (CWE-787) during the parsing of RGB files. By providing a specially crafted RGB file, an attacker can trigger this vulnerability to execute arbitrary code in the context of the current process. The attack vector is local, typically requiring a user to open the malicious file. Autodesk has addressed this in version 2026.3.2.
Affected products
- Autodesk 3ds Max 2026 before 2026.3.2
Timeline
- 2026-02-04: disclosed
- 2026-02-04: advisory
- 2026-02-06: patched: NIST analysis indicates fix in 2026.3.2