What is the CVSS score of CVE-2025-5040?

CVE-2025-5040 has a CVSS 3.1 base score of 7.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Which versions of Revit are affected by CVE-2025-5040?

CVE-2025-5040 is a heap buffer overflow in Autodesk Revit's file parser that allows attackers to execute arbitrary code on affected systems when users open malicious design files.. A patch is available.

How to fix or mitigate CVE-2025-5040?

Within 24 hours: Identify all Revit installations across the organization and document current versions. Within 7 days: Contact Autodesk support to obtain the patched Revit version and deploy it to test environments; establish a baseline inventory of which business units depend on specific Revit versions. Within 30 days: Complete deployment of patched Revit across all endpoints; implement file-origin validation controls requiring users to open RTE files only from trusted internal sources.

Revit CVE-2025-5040

EUVD-2025-20991 HIGH

Heap-based Buffer Overflow (CWE-122)

2025-07-10 psirt@autodesk.com

RCE Information Disclosure Revit

7.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.8 HIGH

AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Updated

Apr 16, 2026 - 06:28 EUVD-patch-fix

executive_summary

Re-analysis Queued

Apr 16, 2026 - 05:29 backfill_euvd_patch

patch_released

Patch available

Apr 16, 2026 - 05:29 EUVD

2023.1.8,2026.2,2025.4.2

EUVD ID Assigned

Mar 16, 2026 - 06:52 euvd

EUVD-2025-20991

Analysis Generated

Mar 16, 2026 - 06:52 vuln.today

CVE Published

Jul 10, 2025 - 12:15 nvd

HIGH 7.8

DescriptionCVE.org

A maliciously crafted RTE file, when parsed through Autodesk Revit, 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.

AnalysisAI

CVE-2025-5040 is a heap-based buffer overflow vulnerability in Autodesk Revit's RTE file parser that allows local attackers with user interaction to trigger memory corruption. Successful exploitation enables arbitrary code execution, sensitive data theft, or application denial of service within the Revit process context. This vulnerability requires a maliciously crafted RTE file and user action to open it, making it a moderate-to-high priority for organizations using Revit for design workflows.

Technical ContextAI

The vulnerability exists in Autodesk Revit's RTE (Revit Template Exchange or similar binary format) file parsing logic, which fails to properly validate buffer boundaries during deserialization. CWE-122 (Heap-based Buffer Overflow) indicates the vulnerability occurs in dynamically allocated memory rather than the stack, potentially allowing attackers to corrupt heap metadata, bypass security mechanisms, or hijack object pointers. The RTE parser likely lacks adequate bounds checking when reading variable-length fields or nested structures from untrusted input, a common issue in legacy CAD file format parsers. Affected CPE would be: cpe:2.3:a:autodesk:revit:*:*:*:*:*:*:*:* (all versions until patched). The vulnerability stems from unsafe memory operations common in C/C++-based CAD applications handling complex binary formats.

RemediationAI

IMMEDIATE: Disable opening untrusted RTE files; educate users not to open RTE files from untrusted sources (email, external file shares). 2. PATCH: Apply Autodesk's security update for Revit once released (check Autodesk Security Advisories at https://www.autodesk.com/trust/security-advisories). Patch version not specified in description; contact Autodesk support for availability. 3. WORKAROUND: Validate RTE files programmatically before opening (requires custom tools or Autodesk guidance). 4. DETECTION: Monitor for suspicious Revit crashes or unexpected memory errors in logs; implement file integrity checking for RTE repositories. 5. NETWORK: Restrict RTE file distribution through email filters if possible; use centralized, scanned file repositories.