CVE-2025-8894
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 · uneditedA maliciously crafted PDF file, when parsed through certain Autodesk products, can force a Heap-Based Overflow vulnerability. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, 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 · high confidenceA heap-based buffer overflow vulnerability exists in certain Autodesk products when parsing maliciously crafted PDF files. The vulnerability allows an attacker to potentially crash the application, read sensitive data from heap memory, or execute arbitrary code within the context of the current process.
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>= 2024, < 2024.1.8>= 2025, < 2025.1.3>= 2026, < 2026.1>= 2024, < 2024.1.8>= 2025, < 2025.1.3>= 2026, < 2026.1>= 2024, < 2024.1.8>= 2025, < 2025.1.3>= 2026, < 2026.1>= 2024, < 2024.1.8>= 2025, < 2025.1.3>= 2026, < 2026.1>= 2025, < 2025.4.3>= 2026, < 2026.3>= 2024, < 2024.1.8>= 2025, < 2025.1.3>= 2026, < 2026.1>= 2024, < 2024.1.8>= 2025, < 2025.1.3>= 2026, < 2026.1>= 2024, < 2024.1.8>= 2025, < 2025.1.3>= 2026, < 2026.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Autodesk productCheck Programs and Features (Windows) or the application menu for the installed Autodesk product name such as AutoCAD, AutoCAD LT, Civil 3D, Plant 3D, Advance Steel, Revit, AutoCAD Architecture, or AutoCAD Electrical.Affected if The installed product is one of the eight affected products listed in the CVE.
-
Determine product version numberOpen the affected Autodesk application, then access Help > About or use the VERSION command in the command line to display the exact version and build number.Affected if The version falls within any of the affected ranges: 2024 versions before 2024.1.8, 2025 versions before 2025.1.3, or 2026 versions before 2026.1 (for most products); for Revit, versions before 2025.4.3 or before 2026.3.
-
Verify PDF import functionality is availableConfirm that the PDF import or PDF underlay feature is enabled in the product. In AutoCAD products, check the PDFIMPORT command or look for PDF underlay options in the Insert tab.Affected if PDF import functionality is present and usable in the installed product.
-
Compare version to vulnerability rangesCross-reference the identified version with the affected version ranges: AutoCAD/AutoCAD LT/Civil 3D/Plant 3D/Advance Steel/AutoCAD Architecture/AutoCAD Electrical: <2024.1.8, <2025.1.3, or <2026.1; Revit: <2025.4.3 or <2026.3.Affected if The installed version is lower than any of the upper bounds in the affected ranges for the corresponding product year.
You are affected if you have any of the listed Autodesk products installed with a version that falls within the specified vulnerable ranges and the PDF import feature is accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2024.1.82025.1.32025.4.3
Users should avoid opening PDF files from untrusted sources. Apply vendor-provided security patches for affected Autodesk products when released.
Upgrade to the minimum fixed version for your product line: AutoCAD/AutoCAD LT/AutoCAD Architecture/AutoCAD Electrical/Advance Steel/Civil 3D/AutoCAD Plant 3D: 2024.1.8, 2025.1.3, or 2026.1 (depending on your release year); Revit: 2025.4.3 or 2026.3 (depending on your release year)
- 1. Identify the specific Autodesk product (e.g., AutoCAD, Revit, Civil 3D, etc.) and current version installed.
- 2. Access Autodesk Account or the product's Help menu to check the current installed version number.
- 3. For AutoCAD, AutoCAD Plant 3D, AutoCAD Architecture, AutoCAD Electrical, Advance Steel, Civil 3D, and AutoCAD LT: upgrade to version 2024.1.8 (or later) for the 2024 release line, OR upgrade to version 2025.1.3 (or later) for the 2025 release line, OR upgrade to version 2026.1 (or later) for the 2026 release line.
- 4. For Revit: upgrade to version 2025.4.3 (or later) for the 2025 release line, OR upgrade to version 2026.3 (or later) for the 2026 release line.
- 5. Download the appropriate update from Autodesk Account (accounts.autodesk.com) or use the product's built-in update mechanism.
- 6. Install the update following Autodesk's standard installation procedure.
- 7. Verify the installed version matches the fixed release after installation.
- 8. Ensure users are warned not to open untrusted or unknown PDF files until the update is applied.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA5.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,216.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8894 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-8894 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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