Code execution via crafted PDF parsing
Published Aug 6, 2026 · Updated Aug 6, 2026
Out-of-bounds write in Autodesk Revit 2024, 2025, 2026, and 2027 allows attackers to execute code through a crafted PDF file. Autodesk identifies the PDF parser as the affected component but has not disclosed the malformed structure or memory operation that writes beyond its intended buffer. Exploitation requires user interaction and runs in the current Revit process, where it can corrupt data, crash the application, or execute arbitrary code.
Summary
What happened
Out-of-bounds write in Autodesk Revit 2024, 2025, 2026, and 2027 allows attackers to execute code through a crafted PDF file. Autodesk identifies the PDF parser as the affected component but has not disclosed the malformed structure or memory operation that writes beyond its intended buffer. Exploitation requires user interaction and runs in the current Revit process, where it can corrupt data, crash the application, or execute arbitrary code.
The record
- CVE
- CVE-2026-8325
- Published
- Aug 6, 2026
- Updated
- Aug 6, 2026
- Vendor
- Autodesk
- Product
- Revit
- Classifications
- CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 6, 2026CVE publishedPublication date reported by the CVE source.
- Aug 6, 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.5.0
- 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