Code execution via crafted DXF heap overflow
Published Jul 29, 2026 · Updated Jul 29, 2026
Heap overflow in DXF parsing in Autodesk AutoCAD, AutoCAD LT, and DWG TrueView 2026 and 2027 allows attackers to execute code. Autodesk has not disclosed the parser routine, malformed DXF field, or missing bounds check that causes the heap overwrite. A user must open the crafted file; successful exploitation runs code in the current process, while other outcomes include sensitive-data reads or a crash.
Summary
What happened
Heap overflow in DXF parsing in Autodesk AutoCAD, AutoCAD LT, and DWG TrueView 2026 and 2027 allows attackers to execute code. Autodesk has not disclosed the parser routine, malformed DXF field, or missing bounds check that causes the heap overwrite. A user must open the crafted file; successful exploitation runs code in the current process, while other outcomes include sensitive-data reads or a crash.
The record
- CVE
- CVE-2026-16463
- Published
- Jul 29, 2026
- Updated
- Jul 29, 2026
- Vendor
- Autodesk
- Product
- AutoCAD
- Classifications
- CWE-122, CAPEC-100, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 29, 2026CVE publishedPublication date reported by the CVE source.
- Jul 29, 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=2027.0.0 <2027.1.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