dbcve.org
RevitApplication · Autodesk

CVE-2025-8893

HIGH · 7.8 CVSS v3.1 Published 2025-09-16
Fix available
A fix is available. Upgrade to 2024.1.8 / 2025.1.3 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an out-of-bounds write vulnerability in Autodesk products' PDF parsing functionality. When a maliciously crafted PDF file is processed, it triggers a memory corruption that can lead to crash, data corruption, or arbitrary code execution in the current process context.

MitigationApply vendor patches from Autodesk when available. Until then, restrict PDF file handling to trusted sources and consider disabling PDF preview features in affected products.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RevitApplication
Affected:>= 2025, < 2025.4.3>= 2026, < 2026.3
AutocadApplication
Affected:>= 2024, < 2024.1.8>= 2025, < 2025.1.3>= 2026, < 2026.1
Autocad ArchitectureApplication
Affected:>= 2024, < 2024.1.8>= 2025, < 2025.1.3>= 2026, < 2026.1
Autocad ElectricalApplication
Affected:>= 2024, < 2024.1.8>= 2025, < 2025.1.3>= 2026, < 2026.1
Autocad MechanicalApplication
Affected:>= 2024, < 2024.1.8>= 2025, < 2025.1.3>= 2026, < 2026.1
Autocad Plant 3dApplication
Affected:>= 2024, < 2024.1.8>= 2025, < 2025.1.3>= 2026, < 2026.1
Advance SteelApplication
Affected:>= 2024, < 2024.1.8>= 2025, < 2025.1.3>= 2026, < 2026.1
Civil 3dApplication
Affected:>= 2024, < 2024.1.8>= 2025, < 2025.1.3>= 2026, < 2026.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Autodesk products
    Check Windows Registry under HKLM\SOFTWARE\Autodesk\ for product folders (Revit, AutoCAD, etc.) or examine Program Files for Autodesk installation directories
    Affected if Any of the following products are present: Revit, AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD Plant 3D, Advance Steel, or Civil 3D
  2. Determine product version
    Open the product's About dialog from the Help menu, or check the executable properties (right-click on the main .exe file, select Properties, view Version tab)
    Affected if Version falls within any of these ranges: Revit 2025 (before 2025.4.3) or 2026 (before 2026.3); AutoCAD/Architecture/Electrical/Mechanical/Plant3D/Advance Steel/Civil3D 2024 (before 2024.1.8), 2025 (before 2025.1.3), or 2026 (before 2026.1)
  3. Confirm PDF functionality is in use
    Check if the product has been used to open or preview PDF files, or verify PDF-related plugins/extensions are loaded
    Affected if The product's PDF import, export, or preview feature has been used or is available on the system

If an affected Autodesk product version is installed AND the PDF parsing feature is accessible, the environment is vulnerable to CVE-2025-8893 when processing untrusted PDF files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2024.1.8 / 2025.1.3 / 2025.4.3 or later
Fixed in 2024.1.82025.1.32025.4.3
Interim mitigation

Apply vendor patches from Autodesk when available. Until then, restrict PDF file handling to trusted sources and consider disabling PDF preview features in affected products.

Recommended fix High confidence

Revit 2025.4.3 / 2026.3; AutoCAD 2024.1.8 / 2025.1.3 / 2026.1 (and corresponding vertical product versions)

  1. 1. Identify the currently installed Autodesk product(s) and version(s) from the affected list (Revit, AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD Plant 3D, Advance Steel, or Civil 3D).
  2. 2. Close all running Autodesk applications.
  3. 3. Download the appropriate fixed version from the official Autodesk website or your Autodesk Account portal: For Revit 2025, upgrade to 2025.4.3 or later; For Revit 2026, upgrade to 2026.3 or later; For AutoCAD 2024, upgrade to 2024.1.8 or later; For AutoCAD 2025, upgrade to 2025.1.3 or later; For AutoCAD 2026, upgrade to 2026.1 or later; For vertical products (Architecture, Electrical, Mechanica
  4. 4. Run the installer with administrator privileges and follow the on-screen prompts to complete the upgrade.
  5. 5. Restart the computer after installation completes.
  6. 6. Launch the updated Autodesk product and verify the version matches the fixed release.
  7. 7. Test that PDF files can be opened normally to confirm functionality is intact.
Caveat Upgrade may require a valid Autodesk subscription; ensure compatibility with existing custom scripts, plugins, and workflows before deploying in production environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Revit Scoped from the published advisory
  • Consultation8.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,920
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,672.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8893 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-8893 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data