Code execution via crafted PDF parsing
Published Apr 15, 2025 · Updated Feb 26, 2026
Memory corruption in Autodesk desktop applications allows context-dependent attackers to execute code through a crafted PDF file. Autodesk identifies the affected locus only as PDF parsing and has not disclosed the malformed PDF structure or memory operation that causes corruption. Exploitation requires a user to open or otherwise parse the file, and resulting code runs with the permissions of the current application process.
Summary
What happened
Memory corruption in Autodesk desktop applications allows context-dependent attackers to execute code through a crafted PDF file. Autodesk identifies the affected locus only as PDF parsing and has not disclosed the malformed PDF structure or memory operation that causes corruption. Exploitation requires a user to open or otherwise parse the file, and resulting code runs with the permissions of the current application process.
The record
- CVE
- CVE-2025-1277
- Published
- Apr 15, 2025
- Updated
- Feb 26, 2026
- Vendor
- Autodesk
- Product
- AutoCAD Mechanical
- Classifications
- CWE-787, CWE-120, T1204.002
- 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.8
- Affected versionversion=2024 <2024.1.8
- Affected versionversion=2025 <2025.1.3
What conditions does exploitation require?
What is affected?
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