Code execution via use-after-free during PDF parsing
Published Aug 6, 2026 · Updated Aug 6, 2026
Use-after-free in Autodesk Revit 2026 before 2026.5.0 and 2027 before 2027.2.0 allows attackers to execute code via a crafted PDF. The PDF parser accesses an object after its memory has been freed, but Autodesk has not disclosed the affected parser routine or object-lifecycle error. A user must open or import the malicious file; exploitation runs in the Revit process and can also disclose process data or crash the application.
Summary
What happened
Use-after-free in Autodesk Revit 2026 before 2026.5.0 and 2027 before 2027.2.0 allows attackers to execute code via a crafted PDF. The PDF parser accesses an object after its memory has been freed, but Autodesk has not disclosed the affected parser routine or object-lifecycle error. A user must open or import the malicious file; exploitation runs in the Revit process and can also disclose process data or crash the application.
The record
- CVE
- CVE-2026-1289
- Published
- Aug 6, 2026
- Updated
- Aug 6, 2026
- Vendor
- Autodesk
- Product
- Revit
- Classifications
- CWE-416, CAPEC-153, T1204.002, T1203
- 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