CVE-2024-12178: Autodesk Navisworks Freedom · Out-of-bounds Write
Affects Autodesk Navisworks FreedomSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Autodesk Navisworks Freedom | Affected
| Fixed in– |
AI-suggested
Organizations should implement strict controls on the handling of DWFX files, including restricting file sources to trusted partners and scanning files with advanced malware detection tools before opening. Until a vendor patch is released, consider sandboxing Navisworks Freedom or running it in isolated environments to limit the impact of potential exploitation. Employ application whitelisting to prevent unauthorized code execution and monitor for unusual process behavior indicative of exploitation attempts. User training should emphasize the risks of opening unsolicited or unexpected DWFX files. Network segmentation can help contain any compromise. Once Autodesk releases a patch, prioritize its deployment across all affected systems. Additionally, maintain up-to-date backups of critical project data to enable recovery in case of an incident.
Description
A maliciously crafted DWFX file, when parsed through Autodesk Navisworks, can force a Memory Corruption vulnerability. A malicious actor can leverage this vulnerability to execute arbitrary code in the context of the current process.