dbcve.org
Infrastructure Parts EditorApplication · Autodesk

CVE-2025-5039

HIGH · 7.8 CVSS v3.1 Published 2025-07-24
Fix available
A fix is available. Upgrade to 2026.0.2 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
A maliciously crafted binary file, when present while loading files in certain Autodesk applications, could lead to execution of arbitrary code in the context of the current process due to an untrusted search path being utilized.

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 · moderate confidence

This is an untrusted search path vulnerability in certain Autodesk applications where a maliciously crafted binary file can be loaded during file operations. Because the application searches for binaries in untrusted locations, an attacker can place a malicious DLL or executable in a directory that gets searched before legitimate locations, leading to arbitrary code execution in the context of the current process.

MitigationApply vendor patches from Autodesk for affected products, ensure application directories are not writable by non-privileged users, and review/secure the DLL search path order to prevent loading from untrusted locations.

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
Infrastructure Parts EditorApplication
Affected:>= 2026, < 2026.0.2
InventorApplication
Affected:>= 2026, < 2026.0.2
Navisworks ManageApplication
Affected:>= 2026, < 2026.0.2
Navisworks SimulateApplication
Affected:>= 2026, < 2026.0.2
RevitApplication
Affected:>= 2026, < 2026.0.2
VaultApplication
Affected:>= 2026, < 2026.0.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Autodesk product
    Open Windows Control Panel > Programs and Features, or use PowerShell: Get-WmiObject -Class Win32_Product | Select-Object Name, Version
    Affected if Any of these products are listed: Infrastructure Parts Editor, Inventor, Navisworks Manage, Navisworks Simulate, Revit, or Vault
  2. Determine the exact version number
    In the Programs and Features list, note the Version column for the Autodesk product, or right-click the application executable in its installation folder and select Properties > Details to view the File Version
    Affected if The version shows as 2026.x where x is any build prior to 2026.0.2, or shows simply as 2026 without the .0.2 patch level
  3. Compare version against affected range
    If version is 2026.0.1, 2026.0.0, or any 2026 release prior to the 2026.0.2 patch, the application is within the vulnerable range. Versions 2025.x or earlier, or 2026.0.2 and later, are not affected
    Affected if Installed version is greater than or equal to 2026 but less than 2026.0.2
  4. Check for writable application directories
    Review folder permissions on the Autodesk application installation directory (typically C:\Program Files\Autodesk\) and ensure standard users cannot write to subdirectories. Use icacls or file explorer Properties > Security to inspect permissions
    Affected if Users with limited privileges can write to directories that the application reads executable files from, increasing exploitability

A user is affected if any of the listed Autodesk products is installed with version 2026.0.0 or 2026.0.1 (any build before 2026.0.2).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2026.0.2 or later
Fixed in 2026.0.2
Interim mitigation

Apply vendor patches from Autodesk for affected products, ensure application directories are not writable by non-privileged users, and review/secure the DLL search path order to prevent loading from untrusted locations.

Recommended fix High confidence

2026.0.2

  1. Identify which Autodesk 2026 products from the affected list are installed (Infrastructure Parts Editor, Inventor, Navisworks Manage, Navisworks Simulate, Revit, Vault)
  2. Back up all current projects, templates, and user settings before updating
  3. Navigate to the official Autodesk website or use Autodesk Account to download the 2026.0.2 update
  4. For each affected product installed, run the 2026.0.2 installer and follow the on-screen prompts to upgrade
  5. Restart the application after installation to ensure all components are properly loaded
  6. Verify the installed version by checking Help > About to confirm version 2026.0.2 is now running

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Infrastructure Parts Editor Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,608.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5039 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-5039 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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