PDF File Parsing Vulnerabilities in Certain Autodesk Desktop Products
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2027.2.0, 2026.5.0, 2025.4.6, 2024.3.6, 2027.1.0, and 3 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A maliciously crafted PDF file, when parsed through Autodesk Revit, can force an Out-of-Bounds Write vulnerability. A malicious actor may leverage this vulnerability to cause a crash, cause data corruption, or execute arbitrary code in the context of the current process.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Autodesk Revit
From 2027.0.0 · fixed in 2027.2.0; From 2026.0.0 · fixed in 2026.5.0; From 2025.0.0 · fixed in 2025.4.6; From 2024.0.0 · fixed in 2024.3.6
- Autodesk AutoCAD
From 2027.0.0 · fixed in 2027.1.0; From 2026.0.0 · fixed in 2026.1.2; From 2025.0.0 · fixed in 2025.1.4; From 2024.0.0 · fixed in 2024.1.9
- Autodesk AutoCAD LT
From 2027.0.0 · fixed in 2027.1.0; From 2026.0.0 · fixed in 2026.1.2; From 2025.0.0 · fixed in 2025.1.4; From 2024.0.0 · fixed in 2024.1.9
- Autodesk DWG TrueView
From 2027.0.0 · fixed in 2027.1.0; From 2026.0.0 · fixed in 2026.1.2; From 2025.0.0 · fixed in 2025.1.4; From 2024.0.0 · fixed in 2024.1.9