dbcve.org
RevitApplication · Autodesk

CVE-2025-1274

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 RCS file, when parsed through Autodesk Revit, 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

Autodesk Revit contains an out-of-bounds write vulnerability when parsing maliciously crafted RCS files. The vulnerability allows a malicious actor to trigger memory corruption by supplying a specially crafted RCS file, potentially leading to crash, data corruption, or arbitrary code execution within the context of the current process.

MitigationApply the vendor patch from Autodesk when available. Until then, avoid opening RCS files from untrusted sources and consider implementing file type validation and sandboxing for Revit's file import functionality.

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 installed Autodesk Revit version
    Open Revit, go to Help > About Autodesk Revit, or run 'revit.exe -version' from command line. The version is displayed in the splash screen or console output.
    Affected if Version is 2023.x < 2023.1.7, OR 2024.x < 2024.3.2, OR 2025.x < 2025.4.1
  2. Confirm RCS file import capability is present
    Check if the Revit installation includes RCS (Revit Cloud Sync) or RVT file handling components. Look for RCS-related add-ins or plugins in the Revit program folder (typically C:\Program Files\Autodesk\Revit 202X).
    Affected if RCS import modules are installed and loaded by Revit
  3. Identify recent RCS file access
    Search user directories for .rcs files opened or synced recently. Check Revit's recent files list, Windows Recent Items folder, and any cloud sync folders (OneDrive, Dropbox) where RCS files may be stored.
    Affected if Users have opened or synced RCS files from any source
  4. Review file type validation settings
    Check if your organization has implemented file type validation or sandboxing for Revit's import functionality. Review Windows Defender Application Control policies or any third-party application control rules targeting Revit.exe.
    Affected if No file type restrictions are configured for .rcs files in Revit

You are affected if your installed Revit version falls within any of the three vulnerable ranges AND your environment processes RCS files, either from user activity or sync operations.

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 the vendor patch from Autodesk when available. Until then, avoid opening RCS files from untrusted sources and consider implementing file type validation and sandboxing for Revit's file import functionality.

Recommended fix High confidence

Revit 2023.1.7, Revit 2024.3.2, or Revit 2025.4.1 (depending on which release line you are on)

  1. Identify the current installed version of Autodesk Revit (Help > About Autodesk Revit)
  2. Determine the appropriate upgrade path based on current version: if 2023.x, upgrade to 2023.1.7 or later; if 2024.x, upgrade to 2024.3.2 or later; if 2025.x, upgrade to 2025.4.1 or later
  3. Navigate to the Autodesk Account portal or official Autodesk support website to download the fixed version
  4. Download the installer for the target fixed release matching your license type (subscription or perpetual)
  5. Close all Autodesk Revit instances and any related processes
  6. Run the installer with appropriate administrative privileges
  7. Follow the on-screen installation prompts to complete the upgrade
  8. Restart the system after installation completes

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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