Skip to main content
CVE-2025-5042VulnerabilityPublished Updated

CVE-2025-5042: Autodesk Revit · Out-of-Bounds Read

Affects Autodesk RevitSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Autodesk RevitAffected
  • =2026
  • =2025
  • =2024
  • =2023
Fixed in–

AI-suggested

1. Monitor Autodesk communications closely for official patches and apply them promptly once released. 2. Until patches are available, implement strict controls on RFA file sources: only open RFA files from trusted, verified sources. 3. Employ network segmentation and endpoint protection to limit the impact of potential exploitation. 4. Use application whitelisting and behavior monitoring to detect anomalous activity related to Revit processes. 5. Educate users about the risks of opening unsolicited or unexpected RFA files, emphasizing phishing and social engineering awareness. 6. Consider sandboxing or opening RFA files in isolated environments to analyze suspicious files safely. 7. Maintain up-to-date backups of critical project data to enable recovery in case of compromise. 8. Review and restrict user privileges to minimize the potential damage from code execution within Revit. 9. Implement file integrity monitoring on directories where RFA files are stored or processed. 10. Collaborate with Autodesk support for guidance and incident response in case of suspected exploitation.

Description

A maliciously crafted RFA file, when parsed through Autodesk Revit, can force an Out-of-Bounds Read 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.

References

Community reviews

Loading reviews…