dbcve.org
Shared ComponentsApplication · Autodesk

CVE-2025-9459

HIGH · 7.8 CVSS v3.1 Published 2025-12-16
Fix available
A fix is available. Upgrade to 2026.5 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 SLDPRT file, when parsed through certain Autodesk products, 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 · moderate confidence

An out-of-bounds read vulnerability exists in multiple Autodesk products when parsing maliciously crafted SLDPRT (SolidWorks part) files. The vulnerability occurs during file parsing logic where insufficient bounds checking allows reading memory beyond allocated buffers, potentially leading to information disclosure or code execution in the current process context.

MitigationApply vendor patches when available; until then, implement controls to prevent opening untrusted SLDPRT files (e.g., email attachment filtering, sandboxing, or user training).

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
Shared ComponentsApplication
Affected:< 2026.5

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 products
    Check system for installed Autodesk applications that use Shared Components (e.g., AutoCAD, Fusion 360, Inventor, Revit, etc.) by reviewing installed programs or running 'Get-ItemProperty' on HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for 64-bit or HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall
    Affected if Any Autodesk product that uses the Shared Components library is installed and the version is below 2026.5
  2. Determine Autodesk Shared Components version
    Locate the Shared Components installation directory (commonly in the Autodesk installation folder under SharedComponents or similar) and check the version of the relevant DLL files (such as AcWebFileHosting.dll, ADMSConsole.dll, or other core components), or use the product's About dialog to find version information
    Affected if The installed Shared Components version is lower than 2026.5
  3. Verify SLDPRT file handling capability
    Check if the software has SolidWorks part file import/insertion capabilities enabled. This may be visible in file association settings, in the software's feature list, or by attempting to identify if SLDPRT-related plugins or translators are present in the installation
    Affected if SLDPRT file parsing modules or translators are present and active in the installation
  4. Review recent file parsing activity
    Examine application logs, temp directories, or crash dumps for evidence of recent SLDPRT file parsing operations, particularly any failures or errors related to SLDPRT file handling that may indicate exploitation attempts
    Affected if SLDPRT files have been recently opened or processed by the affected software

A user is affected if they have any Autodesk product installed with Shared Components version below 2026.5 and the software includes SLDPRT file parsing functionality that can process untrusted files.

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.5 or later
Fixed in 2026.5
Interim mitigation

Apply vendor patches when available; until then, implement controls to prevent opening untrusted SLDPRT files (e.g., email attachment filtering, sandboxing, or user training).

Recommended fix Moderate confidence

2026.5 or later

  1. Upgrade Autodesk software to version 2026.5 or later to resolve the out-of-bounds read vulnerability
  2. Verify the installed version matches or exceeds 2026.5 after upgrade completion
  3. Exercise caution when opening SLDPRT files from untrusted sources, even after patching

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

Fix this in Shared Components Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9459 — 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-9459 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