dbcve.org
Shared ComponentsApplication · Autodesk

CVE-2025-9460

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 certain Autodesk products when parsing SLDPRT (SolidWorks part) files. A maliciously crafted SLDPRT file can trigger the vulnerability, allowing an attacker to read sensitive memory contents or potentially achieve arbitrary code execution within the context of the current process.

MitigationAvoid opening SLDPRT files from untrusted sources and apply vendor-provided security patches for affected Autodesk products once released.

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 the system for installed Autodesk applications (e.g., AutoCAD, Inventor, Maya, 3ds Max, Fusion 360) by reviewing installed programs in Control Panel > Programs and Features, or running 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell
    Affected if Any Autodesk product listed in Programs and Features with a version prior to 2026.5 is installed
  2. Determine Autodesk Shared Components version
    Locate the Autodesk Shared Components installation directory (commonly at C:\Program Files\Autodesk\SharedComponents or within the specific product's installation folder) and check the version of the core DLL files (such as AdWindows.dll, AdPIServices.dll, or similar shared library files) by right-clicking the file, selecting Properties, and reviewing the Details tab
    Affected if The reported version is lower than 2026.5 or the version cannot be determined (file version missing or unretrievable)
  3. Identify SLDPRT file handling capability
    Search the system for any file associations or plugins related to SLDPRT parsing. Check registry keys under HKEY_CLASSES_ROOT\.sldprt and HKEY_LOCAL_MACHINE\SOFTWARE\Classes\SLDPRT to see if Autodesk applications are registered as handlers for this file type
    Affected if SLDPRT file association exists pointing to an affected Autodesk product (version below 2026.5)
  4. Review recent SLDPRT file activity
    Check the Windows Event Viewer under Security and Application logs for recent .sldprt file openings, or inspect the recent files list within Autodesk applications (typically found in the application's recent documents feature) to see if SLDPRT files from external or untrusted sources have been opened
    Affected if Evidence exists of SLDPRT files from unknown or untrusted sources being opened recently on the system

A user is affected if any Autodesk product with Autodesk Shared Components version below 2026.5 is installed and the system has processed or can process SLDPRT 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

Avoid opening SLDPRT files from untrusted sources and apply vendor-provided security patches for affected Autodesk products once released.

Recommended fix Moderate confidence

2026.5

  1. Identify all Autodesk products installed that use the affected Shared Components (including but not limited to AutoCAD, Inventor, Fusion 360, and other design applications)
  2. Check the current version of the installed Autodesk products or Shared Components
  3. Navigate to the official Autodesk support or download page at www.autodesk.com
  4. Download and install the 2026.5 or later version of the affected Autodesk product(s)
  5. Restart any running Autodesk applications
  6. Verify the installed version matches or exceeds 2026.5
Caveat Review Autodesk release notes for compatibility with existing projects and workflows before upgrading production systems

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

Fix this in Shared Components Scoped from the published advisory
  • Consultation3.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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