Code execution via out-of-bounds RGB parser write
Published Feb 4, 2026 · Updated Feb 4, 2026
Memory corruption in Autodesk 3ds Max 2026 before 2026.3.2 allows local users to execute code by processing a crafted RGB file. The RGB parser performs an out-of-bounds write while processing malformed RGB data, corrupting memory in the current process. Attackers must cause 3ds Max to process the file; successful exploitation runs with the privileges of that process.
Summary
What happened
Memory corruption in Autodesk 3ds Max 2026 before 2026.3.2 allows local users to execute code by processing a crafted RGB file. The RGB parser performs an out-of-bounds write while processing malformed RGB data, corrupting memory in the current process. Attackers must cause 3ds Max to process the file; successful exploitation runs with the privileges of that process.
The record
- CVE
- CVE-2026-0661
- Published
- Feb 4, 2026
- Updated
- Feb 4, 2026
- Vendor
- Autodesk
- Product
- 3ds Max
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Feb 4, 2026CVE publishedPublication date reported by the CVE source.
- Feb 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2026 <2026.3.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo