Current-process code execution via crafted ABC file
Published Aug 24, 2026 · Updated Aug 24, 2026
Out-of-bounds write in Autodesk 3ds Max 2026 and 2027 allows attackers to execute code when a user opens a crafted ABC file. The ABC file parser writes beyond an allocated buffer while processing attacker-controlled file data; Autodesk has not disclosed the responsible function or field. Successful exploitation requires user interaction and runs code in the current 3ds Max process; malformed input can instead corrupt data or crash the application.
Summary
What happened
Out-of-bounds write in Autodesk 3ds Max 2026 and 2027 allows attackers to execute code when a user opens a crafted ABC file. The ABC file parser writes beyond an allocated buffer while processing attacker-controlled file data; Autodesk has not disclosed the responsible function or field. Successful exploitation requires user interaction and runs code in the current 3ds Max process; malformed input can instead corrupt data or crash the application.
The record
- CVE
- CVE-2026-16783
- Published
- Aug 24, 2026
- Updated
- Aug 24, 2026
- Vendor
- Autodesk
- Product
- 3ds Max
- Classifications
- CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 2026CVE publishedPublication date reported by the CVE source.
- Aug 24, 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.0.0 <2026.3.4
- Affected versionversion=2027.0.0 <2027.2.0
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