Code execution via crafted DWG parsing
Published Apr 15, 2025 · Updated Feb 26, 2026
Out-of-bounds write in Autodesk DWG parsing in affected 2023–2025 desktop products allows attackers to execute code via a crafted DWG file. Autodesk has not disclosed the parser component or the unchecked length, offset, or allocation operation that permits the write beyond a buffer boundary. A user must open or otherwise parse the file; exploitation runs in the current process and can also crash it or corrupt data.
Summary
What happened
Out-of-bounds write in Autodesk DWG parsing in affected 2023–2025 desktop products allows attackers to execute code via a crafted DWG file. Autodesk has not disclosed the parser component or the unchecked length, offset, or allocation operation that permits the write beyond a buffer boundary. A user must open or otherwise parse the file; exploitation runs in the current process and can also crash it or corrupt data.
The record
- CVE
- CVE-2025-1276
- Published
- Apr 15, 2025
- Updated
- Feb 26, 2026
- Vendor
- Autodesk
- Product
- AutoCAD Mechanical
- Classifications
- CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 15, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 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=2023 <2023.1.7
- Affected versionversion=2024 <2024.1.7
- Affected versionversion=2025 <2025.1.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.
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