CVE-2024-12191
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, may force an Out-of-Bounds Write 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.
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 confidenceA crafted DWFX file parsed by Autodesk Navisworks triggers an out-of-bounds write vulnerability, allowing potential crash, data corruption, or arbitrary code execution in the current process context.
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.4CVSS 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 if Autodesk Navisworks is installedLook for Navisworks installation in typical locations: C:\Program Files\Autodesk\Navisworks or use system inventory tools like SCCM, registry searches (HKLM\SOFTWARE\Autodesk\Navisworks), or installed programs list.Affected if Navisworks is installed on the system
-
Determine the installed Navisworks versionLocate the main executable (typically Navisworks.exe) in the installation folder, right-click and view Properties, or check the version in Add/Remove Programs. The version is usually displayed as a four-part number like 2025.x.x.x.Affected if Unable to determine the version (assume potentially affected)
-
Compare version against affected rangeCompare the installed version number to the affected range: versions 2025.0.0 through 2025.3.x are vulnerable. Versions below 2025 or at 2025.4 and above are not affected by this CVE.Affected if Installed version is 2025.0.0 or higher but lower than 2025.4.0
-
Identify DWFX file handling exposureDetermine if users routinely import or open DWFX files in Navisworks. DWFX is a Design Web Format file used for design review. Check for recent imports or configured file folders.Affected if Users open DWFX files from untrusted or external sources in the affected Navisworks version
The system is affected if Autodesk Navisworks version 2025.0 through 2025.3 is installed and users open DWFX files, since the vulnerability triggers during DWFX file parsing.
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.4
Users should avoid opening untrusted DWFX files until a vendor patch is available; organizations should implement file scanning and sandboxing for imported design files.
Navisworks 2025.4
- Navigate to Autodesk's official support or download page for Navisworks
- Download Navisworks version 2025.4 or later
- Run the installer and follow Autodesk's standard installation procedures to update the software
- Restart Navisworks after installation completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12191 — 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-2024-12191 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