CVE-2025-1659
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA maliciously crafted DWFX file, when parsed through Autodesk Navisworks, 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAutodesk Navisworks contains an out-of-bounds read vulnerability when parsing maliciously crafted DWFX files. An attacker can exploit this by enticing a user to open a specially crafted DWFX file, potentially leading to crash, sensitive data disclosure, or arbitrary code execution in the context of the current process.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2025, < 2025.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Navisworks versionOpen Navisworks, then go to Help > About Autodesk Navisworks. Note the full version number displayed (e.g., 2025.0, 2025.1, 2025.2, etc.). Alternatively, right-click the Navisworks executable in Program Files, select Properties, and view the File Version details.Affected if The installed version is 2025.0 through 2025.4 (any version >= 2025 but < 2025.5)
-
Confirm DWFX file handling is activeAttempt to open a sample DWFX file in Navisworks, or verify that .dwfx file association is configured. The vulnerability triggers when Navisworks parses DWFX content, which is a built-in capability enabled by default.Affected if DWFX file parsing is enabled (default state) - the check passes if you can open DWFX files in Navisworks
-
Identify user exposure to untrusted DWFX filesAudit recent file open activity in Navisworks by checking the application log or recent documents list. Determine whether users routinely open DWFX files from external or untrusted sources.Affected if Users have opened or are likely to open DWFX files from untrusted or external sources
You are affected if Navisworks 2025.x (x < 5) is installed AND DWFX file parsing is enabled, allowing users to open potentially malicious DWFX files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2025.5
Apply the vendor patch from Autodesk when available. As an interim control, disable or restrict the ability to open DWFX files from untrusted sources, or run Navisworks in an isolated sandbox environment.
Navisworks 2025.5
- Back up all important project files and settings before proceeding with the update
- Navigate to the Autodesk Account or official Autodesk support page to obtain the Navisworks 2025.5 update
- Download the Navisworks 2025.5 installer or update package
- Run the installer and follow the on-screen prompts to complete the installation
- Restart the application after installation completes
- Verify that the installed version shows 2025.5 and test with previously affected DWFX files
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1659 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-1659 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data