Code execution via out-of-bounds PDF parser write
Published Sep 16, 2025 · Updated Sep 16, 2025
Out-of-bounds write in Autodesk desktop products allows attackers to execute code when a malicious PDF file is opened. Autodesk identifies PDF parsing as the locus but has not disclosed the specific parser routine or bounds-check failure that writes beyond an allocated buffer. Exploitation requires user interaction and runs code in the current process; the same write can instead corrupt data or crash the application.
Summary
What happened
Out-of-bounds write in Autodesk desktop products allows attackers to execute code when a malicious PDF file is opened. Autodesk identifies PDF parsing as the locus but has not disclosed the specific parser routine or bounds-check failure that writes beyond an allocated buffer. Exploitation requires user interaction and runs code in the current process; the same write can instead corrupt data or crash the application.
The record
- CVE
- CVE-2025-8893
- Published
- Sep 16, 2025
- Updated
- Sep 16, 2025
- Vendor
- Autodesk
- Product
- AutoCAD Mechanical
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 16, 2025CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=2025 <2025.1.3
- Affected versionversion=2026 <2026.1
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.
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