CVE Alert: CVE-2025-8893 – Autodesk – Revit

CVE-2025-8893

HIGHNo exploitation known

A maliciously crafted PDF file, when parsed through certain Autodesk products, 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.

CVSS v3.1 (7.8)
AV LOCAL · AC LOW · PR NONE · UI REQUIRED · S UNCHANGED
Vendor
Autodesk, Autodesk, Autodesk, Autodesk, Autodesk, Autodesk, Autodesk, Autodesk, Autodesk, Autodesk, Autodesk
Product
Revit, AutoCAD, AutoCAD LT, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, AutoCAD MAP 3D, Civil 3D, Advance Steel
Versions
2026 lt 2026.3 | 2025 lt 2025.4.3 | 2026 lt 2026.1 | 2025 lt 2025.1.3 | 2026 lt 2026.1 | 2025 lt 2025.1.3 | 2026 lt 2026.1 | 2025 lt 2025.1.3 | 2026 lt 2026.1 | 2025 lt 2025.1.3 | 2026 lt 2026.1 | 2025 lt 2025.1.3 | 2026 lt 2026.1 | 2025 lt 2025.1.3 | 2026 lt 2026.1 | 2025 lt 2025.1.3 | 2026 lt 2026.1 | 2025 lt 2025.1.3 | 2026 lt 2026.1 | 2025 lt 2025.1.3 | 2026 lt 2026.1 | 2025 lt 2025.1.3
CWE
CWE-787, CWE-787 Out-of-Bounds Write
Vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Published
2025-09-16T14:17:05.441Z
Updated
2025-09-16T14:41:19.665Z
cpe:2.3:a:autodesk:revit:2026:*:*:*:*:*:*:*cpe:2.3:a:autodesk:revit:2025:*:*:*:*:*:*:*cpe:2.3:a:autodesk:autocad:2026:*:*:*:*:*:*:*cpe:2.3:a:autodesk:autocad:2025:*:*:*:*:*:*:*cpe:2.3:a:autodesk:autocad_lt:2026:*:*:*:*:*:*:*cpe:2.3:a:autodesk:autocad_lt:2025:*:*:*:*:*:*:*cpe:2.3:a:autodesk:autocad_architecture:2026:*:*:*:*:*:*:*cpe:2.3:a:autodesk:autocad_architecture:2025:*:*:*:*:*:*:*cpe:2.3:a:autodesk:autocad_electrical:2026:*:*:*:*:*:*:*cpe:2.3:a:autodesk:autocad_electrical:2025:*:*:*:*:*:*:*cpe:2.3:a:autodesk:autocad_mechanical:2026:*:*:*:*:*:*:*cpe:2.3:a:autodesk:autocad_mechanical:2025:*:*:*:*:*:*:*cpe:2.3:a:autodesk:autocad_mep:2026:*:*:*:*:*:*:*cpe:2.3:a:autodesk:autocad_mep:2025:*:*:*:*:*:*:*cpe:2.3:a:autodesk:autocad_plant_3d:2026:*:*:*:*:*:*:*cpe:2.3:a:autodesk:autocad_plant_3d:2025:*:*:*:*:*:*:*cpe:2.3:a:autodesk:autocad_map_3d:2026:*:*:*:*:*:*:*cpe:2.3:a:autodesk:autocad_map_3d:2025:*:*:*:*:*:*:*cpe:2.3:a:autodesk:civil_3d:2026:*:*:*:*:*:*:*cpe:2.3:a:autodesk:civil_3d:2025:*:*:*:*:*:*:*cpe:2.3:a:autodesk:advance_steel:2026:*:*:*:*:*:*:*cpe:2.3:a:autodesk:advance_steel:2025:*:*:*:*:*:*:*

AI Summary Analysis

Risk verdict

High risk of local code execution through a crafted PDF parsed by the CAD/BIM tool suite; exploitation is not shown as active, but patching should be executed promptly.

Why this matters

If exploited, attackers could corrupt data, exfiltrate or tamper design work, or disrupt workflows. The widespread use of these tools on Windows endpoints means a single phishing PDF could compromise multiple workstations across teams.

Most likely attack path

An attacker must persuade a user to open a malicious PDF in the affected software; no special privileges are required, but user interaction is necessary. Once opened, code execution would occur in the user’s context, with a high chance of a crash or arbitrary code execution within the local process.

Who is most exposed

Organizations deploying CAD/BIM tool suites on Windows across design, architecture or engineering workflows are most at risk, especially those with shared design repositories and contractor access.

Detection ideas

  • Crashes or crash dumps in the PDF parsing component after opening a PDF.
  • Windows event logs or crash reports noting memory access violations.
  • Anomalous memory or CPU spikes in the CAD/BIM process following PDF delivery.
  • EDR alerts for unusual activity in the PDF parsing process.
  • Phishing emails with PDF attachments targeting design teams.

Mitigation and prioritisation

  • Apply the latest vendor security update (2026.3 or newer) and verify patch success.
  • Enforce least-privilege and sandboxing for the parsing process; disable auto-run of embedded content where possible.
  • Enable OS mitigations (DEP/ASLR) and keep security tooling up to date.
  • Use application whitelisting and robust phishing controls; provide user awareness training.
  • Plan staged deployment with testing in a controlled environment; ensure backup integrity beforehand.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on “Patreon” or “Buy Me A Coffee” using the buttons below

To keep up to date follow us on the below channels.