dbcve.org
RevitApplication · Autodesk

CVE-2025-5036

HIGH · 7.8 CVSS v3.1 Published 2025-06-02
Fix available
A fix is available. Upgrade to 2024.3.3 / 2025.4.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 RFA file, when linked or imported into Autodesk Revit, can force a Use-After-Free 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 confidence

A maliciously crafted RFA (Revit Family) file, when linked or imported into Autodesk Revit, triggers a Use-After-Free memory corruption vulnerability. The vulnerability allows an attacker to potentially crash the application, leak sensitive memory contents, or achieve arbitrary code execution within the current process context.

MitigationAvoid opening or importing RFA files from untrusted sources. Monitor for and apply vendor patches from Autodesk when released. Consider implementing file type validation or sandboxing for RFA import operations 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:>= 2024, < 2024.3.3>= 2025, < 2025.4.2>= 2026, < 2026.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 for Revit installation directory (typically C:\Program Files\Autodesk\Revit 202X) or look for Revit executable (Revit.exe) on the system
    Affected if Autodesk Revit is found on the system
  2. Determine installed Revit version
    Right-click on Revit.exe in the installation folder, select Properties, then view the Details tab for Product version, or run 'Revit /version' from command prompt if installed
    Affected if Version cannot be determined or falls within affected ranges
  3. Compare version against affected ranges
    Match the installed version number against: 2024 (versions < 2024.3.3), 2025 (versions < 2025.4.2), or 2026 (versions < 2026.1)
    Affected if Installed version is >= 2024 but < 2024.3.3, OR >= 2025 but < 2025.4.2, OR >= 2026 but < 2026.1
  4. Check for RFA file import or linking activity
    Monitor for user activity involving importing or linking RFA (Revit Family) files into Revit projects, or check recent file access logs for .rfa extensions
    Affected if RFA files from untrusted sources are being imported or linked into Revit projects

User is affected if Autodesk Revit is installed with a version matching the affected ranges AND RFA files are being processed, as the vulnerability requires both conditions to be exploitable.

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 2024.3.3 / 2025.4.2 / 2026.1 or later
Fixed in 2024.3.32025.4.22026.1
Interim mitigation

Avoid opening or importing RFA files from untrusted sources. Monitor for and apply vendor patches from Autodesk when released. Consider implementing file type validation or sandboxing for RFA import operations as a defense-in-depth measure.

Recommended fix High confidence

Revit 2024.3.3 or later; Revit 2025.4.2 or later; Revit 2026.1 or later

  1. Back up all project files and RFA families before updating
  2. Close Autodesk Revit completely
  3. Download the fixed version from Autodesk's official website: 2024.3.3 (or later), 2025.4.2 (or later), or 2026.1 (or later) depending on your current major version
  4. Run the installer and follow the on-screen instructions to update Revit
  5. After installation, verify the update by checking Help > About Autodesk Revit to confirm the version number
  6. Test importing or linking RFA files that previously caused issues or were from untrusted sources
Caveat Review Autodesk's release notes for your specific version upgrade for any changes to family behavior or API compatibility

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-5036 — 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-5036 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