dbcve.org
RevitApplication · Autodesk

CVE-2025-1277

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 parsed through Autodesk applications, can force a Memory Corruption vulnerability. A malicious actor can leverage this vulnerability to 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 vulnerability involves memory corruption when Autodesk applications parse maliciously crafted PDF files. The flaw allows arbitrary code execution within the current process context, making it exploitable through relatively simple PDF-based attack vectors.

MitigationApply vendor-supplied patches for affected Autodesk products once available; until then, restrict PDF file handling to trusted sources and implement endpoint protection to scan potentially malicious files.

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. Check if Autodesk Revit is installed
    Open Windows Control Panel > Programs and Features, or use PowerShell command: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion | Where-Object {$_.DisplayName -like '*Revit*'}
    Affected if Autodesk Revit is present on the system
  2. Identify the installed Revit version number
    In Revit, go to Help > About Autodesk Revit, or check the version in Programs and Features, or run: (Get-Item 'C:\Program Files\Autodesk\Revit *\Revit.exe').VersionInfo.FileVersion
    Affected if The version is 2023.x before 2023.1.7, OR 2024.x before 2024.3.2, OR 2025.x before 2025.4.1
  3. Determine if PDF import/linking is in use
    In Revit, check Recent Files or open a project and use Insert > Link CAD or PDF to see if PDF functionality is utilized, or inspect project workflows for PDF import workflows
    Affected if Users regularly import, link, or otherwise process PDF files within Revit projects
  4. Verify PDF handling occurs without sandboxing
    Review whether PDF files are opened directly in Revit without additional sandboxing, virus scanning, or restricted file handling policies
    Affected if PDF files are handled directly by Revit from untrusted or external sources without additional protective measures

You are affected if Autodesk Revit is installed with a version matching 2023.x < 2023.1.7, 2024.x < 2024.3.2, or 2025.x < 2025.4.1 AND the application processes PDF files from potentially untrusted sources.

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

Apply vendor-supplied patches for affected Autodesk products once available; until then, restrict PDF file handling to trusted sources and implement endpoint protection to scan potentially malicious files.

Recommended fix Moderate confidence

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

  1. Identify the current installed version of Autodesk Revit (2023, 2024, or 2025)
  2. Close any running instances of Autodesk Revit
  3. Obtain the appropriate fixed version from the official Autodesk website or your licensing portal
  4. For Revit 2023: Upgrade to version 2023.1.7 or later
  5. For Revit 2024: Upgrade to version 2024.3.2 or later
  6. For Revit 2025: Upgrade to version 2025.4.1 or later
  7. Run the installer with administrator privileges
  8. Restart the workstation after installation completes
Caveat Review Autodesk Revit release notes for your version for potential workflow, family compatibility, or API changes before 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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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