dbcve.org
RevitApplication · Autodesk

CVE-2025-1273

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

A heap-based buffer overflow vulnerability exists in multiple Autodesk applications when processing maliciously crafted PDF files that are linked or imported. The vulnerability allows a remote attacker to execute arbitrary code in the context of the current process by leveraging the heap overflow to overwrite memory locations.

MitigationAvoid opening or importing PDF files from untrusted or unknown sources in affected Autodesk applications. Apply vendor patches when available and implement application sandboxing or file type restrictions as a defense-in-depth measure.

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. Confirm Autodesk Revit installation
    Check for Revit installation by looking for the executable (Revit.exe) in typical installation paths such as C:\Program Files\Autodesk\Revit 2023, C:\Program Files\Autodesk\Revit 2024, or C:\Program Files\Autodesk\Revit 2025. You can also check Add/Remove Programs on Windows or use command: dir /s "C:\Program Files\Autodesk\Revit*" 2>nul
    Affected if Revit is not installed on the system
  2. Determine installed Revit version
    Right-click on the Revit.exe file, select Properties, then view the Details tab to see the Product version. Alternatively, open Revit and go to Help > About Autodesk Revit to view the exact version number including the build number
    Affected if The version number is not displayed or cannot be determined
  3. Compare version against affected ranges
    Compare your installed version (e.g., 2023.1.5, 2024.2.1, 2025.3.0) against the vulnerable ranges: 2023 versions before 2023.1.7, 2024 versions before 2024.3.2, and 2025 versions before 2025.4.1
    Affected if The installed version falls within any of these ranges: >= 2023 and < 2023.1.7, OR >= 2024 and < 2024.3.2, OR >= 2025 and < 2025.4.1
  4. Verify PDF import/link feature usage
    Check if users have imported or linked PDF files into Revit projects. Review recent project files or check Revit usage logs for PDF-related operations. On Windows, search for .pdf files in project directories or check the Links panel in Revit for attached PDF under the Import/Link function
    Affected if PDF files are being imported or linked into Revit projects

A user is affected if Autodesk Revit is installed with a version matching the affected ranges AND PDF files are being imported or linked into the application.

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 in affected Autodesk applications. Apply vendor patches when available and implement application sandboxing or file type restrictions as a defense-in-depth measure.

Recommended fix High confidence

Revit 2023.1.7, Revit 2024.3.2, or Revit 2025.4.1 (depending on your version line)

  1. 1. Open Revit and go to Help > About Autodesk Revit to check your current version number
  2. 2. Navigate to the Autodesk Account or Support portal at www.autodesk.com to download the appropriate fixed release for your version line
  3. 3. For Revit 2023 users: Download and install version 2023.1.7 or later
  4. 4. For Revit 2024 users: Download and install version 2024.3.2 or later
  5. 5. For Revit 2025 users: Download and install version 2025.4.1 or later
  6. 6. Restart Revit after installation completes
  7. 7. Verify the installed version matches or exceeds the fixed release (Help > About Autodesk Revit)
Caveat Review Autodesk's release notes for your specific version upgrade for any compatibility notes or workflow changes

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

Fix this in Revit Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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