Code execution via JPG parser out-of-bounds write
Published Nov 12, 2025 · Updated Nov 12, 2025
Out-of-bounds write in Autodesk 3ds Max 2026 through 2026.2 allows attackers to execute code through a crafted JPG file. The JPG parsing path writes outside its intended memory bounds while processing malformed image data; Autodesk has not disclosed the affected module or function. Exploitation requires user interaction that causes 3ds Max to parse the file, and successful code runs in the context of the current process.
Summary
What happened
Out-of-bounds write in Autodesk 3ds Max 2026 through 2026.2 allows attackers to execute code through a crafted JPG file. The JPG parsing path writes outside its intended memory bounds while processing malformed image data; Autodesk has not disclosed the affected module or function. Exploitation requires user interaction that causes 3ds Max to parse the file, and successful code runs in the context of the current process.
The record
- CVE
- CVE-2025-11795
- Published
- Nov 12, 2025
- Updated
- Nov 12, 2025
- Vendor
- Autodesk
- Product
- 3ds Max
- Classifications
- CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 12, 2025CVE publishedPublication date reported by the CVE source.
- Nov 12, 2025Record 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
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.
Weakness, pattern, technique
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