Skip to main content
CVE-2025-8354VulnerabilityPublished Updated

CVE-2025-8354: Autodesk Revit · Type Confusion

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 7% 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 23 Sep 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
Fixed in–

AI-suggested

1. Immediately apply any patches or updates released by Autodesk once available. 2. Until patches are released, restrict the opening of RFA files from untrusted or unknown sources. 3. Implement strict file validation and scanning for RFA files using endpoint protection solutions that can detect malformed or suspicious files. 4. Educate users on the risks of opening unsolicited or unexpected Revit files, emphasizing caution with email attachments and downloads. 5. Use application whitelisting and sandboxing techniques to limit the impact of potential exploitation. 6. Monitor system and network logs for unusual activity related to Revit processes, such as unexpected crashes or anomalous behavior. 7. Consider network segmentation to isolate systems running Revit to reduce lateral movement risk. 8. Employ least privilege principles for user accounts running Revit to minimize the impact of code execution within the process context. 9. Coordinate with Autodesk support for guidance and early access to patches or workarounds if available.

Description

A maliciously crafted RFA file, when parsed through Autodesk Revit, can force a Type Confusion 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.

References

Community reviews

Loading reviews…