CVE-2025-1660: DWFX File Parsing Memory Corruption Vulnerability
First published: Tue Apr 01 2025(Updated: )
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.
Credit: psirt@autodesk.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Autodesk Navisworks |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2025-1660?
CVE-2025-1660 has a high severity rating due to its potential to allow arbitrary code execution.
How do I fix CVE-2025-1660?
To fix CVE-2025-1660, ensure that you update Autodesk Navisworks to the latest version provided by the vendor.
Can CVE-2025-1660 be exploited remotely?
CVE-2025-1660 requires a user to open a maliciously crafted DWFX file to be exploited, thus it is not a remote exploit.
What are the potential impacts of CVE-2025-1660?
The impact of CVE-2025-1660 includes the possibility of memory corruption and the execution of arbitrary code.
Is there a workaround for CVE-2025-1660?
Currently, there are no known workarounds for CVE-2025-1660, and it is recommended to apply the security update to mitigate the risk.
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/references
- agent/title
- agent/type
- agent/description
- agent/first-publish-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/author
- agent/source
- agent/last-modified-date
- agent/severity
- agent/tags
- agent/event
- vendor/autodesk
- canonical/autodesk navisworks