dbcve.org
RevitApplication · Autodesk

CVE-2025-1656

HIGH · 7.8 CVSS v3.1 Published 2025-04-15
Fix available
A fix is available. Upgrade to 2023.1.7 / 2024.3.2 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 linked or imported into Autodesk applications, 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 · moderate confidence

This is a heap-based buffer overflow vulnerability in Autodesk applications triggered by importing or linking maliciously crafted PDF files. The vulnerability allows a remote attacker to potentially crash the application, read sensitive data from heap memory, or achieve arbitrary code execution within the context of the running process.

MitigationAvoid opening or importing PDF files from untrusted or unknown sources until an official vendor patch is available. Implement application sandboxing and ensure Autodesk applications are running with the least privilege necessary.

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:>= 2023, < 2023.1.7>= 2024, < 2024.3.2>= 2025, < 2025.4.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 if Autodesk Revit is installed
    Check the system for Autodesk Revit installation by looking for the application in Program Files (e.g., C:\Program Files\Autodesk\Revit [version]) or by searching for Revit.exe via file explorer or command line (e.g., dir /s C:\Revit.exe)
    Affected if Autodesk Revit is not found on the system, then not affected
  2. Determine the installed Revit version
    Open Autodesk Revit and navigate to Help > About Autodesk Revit, or check the installation folder name which typically includes the version number (e.g., 'Revit 2023', 'Revit 2024', 'Revit 2025')
    Affected if The installed version falls within these ranges: 2023.0 to 2023.1.6, 2024.0 to 2024.3.1, or 2025.0 to 2025.4.0
  3. Confirm PDF import or link functionality is accessible
    In Autodesk Revit, try to access the PDF import feature: go to Insert > Import PDF or check if PDF under the Import options is available in the Insert tab
    Affected if PDF import or link options are present and accessible in the application UI, indicating the vulnerable feature is available for use
  4. Review recent PDF imports
    Check the Revit project history, recent activity logs, or the user\'s recent documents folder for any recently imported or linked PDF files that may have originated from untrusted sources
    Affected if PDF files from untrusted or unknown sources have been imported into recent projects

A user is affected if they have Autodesk Revit installed with a version within 2023.0-2023.1.6, 2024.0-2024.3.1, or 2025.0-2025.4.0 and have used or may use the PDF import/link feature.

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 2023.1.7 / 2024.3.2 / 2025.4.1 or later
Fixed in 2023.1.72024.3.22025.4.1
Interim mitigation

Avoid opening or importing PDF files from untrusted or unknown sources until an official vendor patch is available. Implement application sandboxing and ensure Autodesk applications are running with the least privilege necessary.

Recommended fix High confidence

For Revit 2023: upgrade to 2023.1.7 or later; For Revit 2024: upgrade to 2024.3.2 or later; For Revit 2025: upgrade to 2025.4.1 or later

  1. 1. Back up all Revit projects and settings before updating
  2. 2. Download the appropriate fixed version of Autodesk Revit from the official Autodesk website (www.autodesk.com)
  3. 3. Ensure all Revit instances are closed before installation
  4. 4. Run the installer with administrator privileges
  5. 5. Follow the on-screen installation prompts to complete the update
  6. 6. After installation, verify the version by going to Help > About Autodesk Revit to confirm the installed version matches the fixed release
Caveat Autodesk product updates may include file format changes; older project files should remain compatible but test critical files after upgrading

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

Fix this in Revit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1656 — 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-1656 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