dbcve.org
RevitApplication · Autodesk

CVE-2025-2497

HIGH · 7.8 CVSS v3.1 Published 2025-04-15
Fix available
A fix is available. Upgrade to 2024.3.2 / 2025.4.1 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 DWG file, when parsed through Autodesk Revit, can cause a Stack-Based Buffer Overflow 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 · high confidence

A stack-based buffer overflow vulnerability exists in Autodesk Revit's DWG file parsing functionality. When processing a maliciously crafted DWG file, the application fails to properly validate buffer boundaries, allowing an attacker to overwrite stack memory and achieve arbitrary code execution in the context of the current process.

MitigationApply the vendor patch from Autodesk when available. Until then, avoid opening DWG files from untrusted sources, disable DWG preview handlers, and consider running Revit in isolated environments for high-risk file operations.

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.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
    Look for Revit installation in Program Files, or check for Revit shortcuts in the Start menu or Desktop. The typical install path is C:\Program Files\Autodesk\Revit <version>\
    Affected if Revit is installed on the system
  2. Determine the installed Revit version number
    Right-click on the Revit executable (Revit.exe) in the installation folder, select Properties, and view the File Version field in the Details tab. Alternatively, open Revit and go to Help > About Autodesk Revit to see the exact version number.
    Affected if The version shown is >= 2024 but < 2024.3.2, or >= 2025 but < 2025.4.1
  3. Verify the DWG parsing component is present
    Confirm the Revit installation includes the DWG import/export functionality. Check for DWG-related DLLs in the Revit program folder, such as AecBaseDWG.dll or similar DWG-related components.
    Affected if DWG file handling modules are present in the installation
  4. Confirm DWG files are processed by this installation
    Review whether the Revit installation is used in your workflow to open, import, or preview DWG files from external sources.
    Affected if Users routinely open DWG files from external or untrusted sources using this Revit installation

You are affected if Autodesk Revit is installed with a version in the range 2024.0 to 2024.3.1 or 2025.0 to 2025.4.0, and the DWG parsing functionality is available and used.

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.2 / 2025.4.1 or later
Fixed in 2024.3.22025.4.1
Interim mitigation

Apply the vendor patch from Autodesk when available. Until then, avoid opening DWG files from untrusted sources, disable DWG preview handlers, and consider running Revit in isolated environments for high-risk file operations.

Recommended fix High confidence

Revit 2024.3.2 or later, or Revit 2025.4.1 or later

  1. Upgrade Autodesk Revit to version 2024.3.2 or later for the 2024 release line
  2. Alternatively, upgrade to version 2025.4.1 or later for the 2025 release line
  3. Ensure the upgrade is applied on all systems that parse DWG files through Autodesk Revit
  4. After upgrading, verify that the DWG parsing functionality works correctly
Caveat Review Autodesk Revit release notes for the chosen version to check for any changes that may affect workflows

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

Fix this in Revit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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