dbcve.org
Shared ComponentsApplication · Autodesk

CVE-2025-9456

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 a Memory corruption vulnerability. A malicious actor can leverage this vulnerability to 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

A memory corruption vulnerability exists in certain Autodesk products when parsing maliciously crafted SLDPRT (SolidWorks part) files. The vulnerability allows an attacker to execute arbitrary code in the context of the current process via a specially crafted file.

MitigationApply vendor-supplied security patches to affected Autodesk products when released, and implement file origin verification to avoid opening untrusted SLDPRT files from unknown or unverified sources.

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 for Autodesk applications in Program Files (e.g., C:\Program Files\Autodesk) or use PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.Publisher -like '*Autodesk*'} | Select-Object DisplayName, DisplayVersion
    Affected if any Autodesk product that handles SLDPRT files is present on the system
  2. Locate Autodesk Shared Components version
    Search for files named 'adSSO.dll', 'AdAppManager.dll', or similar shared component DLLs in the Autodesk installation directory, then right-click the file > Properties > Details to view the version. Alternatively, check the version of the main Autodesk application executable.
    Affected if the shared component version shown is below 2026.5
  3. Confirm SLDPRT file association with Autodesk software
    Check if .sldPRT files are associated with any installed Autodesk product by right-clicking a SLDPRT file > Properties > Opens with, or by searching file associations in Windows Registry under HKCR:\.sldPRT
    Affected if Autodesk software is the default handler for SLDPRT files
  4. Verify the vulnerable parsing component exists
    Examine the Autodesk installation folder for components that handle SLDPRT parsing, typically found in subfolders like 'bin' or within the main program directory. Check file timestamps and versions of parsing-related DLLs if visible.
    Affected if SLDPRT parsing components are present in the Autodesk installation
  5. Compare installed version against vulnerability threshold
    If a version number was obtained from the Autodesk product or shared components, verify whether it is below 2026.5 (the fixed version)
    Affected if the installed version is 2026.4 or lower, or any version below 2026.5

A system is affected if it has any Autodesk product installed that can open SLDPRT files and the Autodesk Shared Components version is below 2026.5.

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-supplied security patches to affected Autodesk products when released, and implement file origin verification to avoid opening untrusted SLDPRT files from unknown or unverified sources.

Recommended fix Moderate confidence

2026.5

  1. Identify the specific Autodesk product(s) in use that utilize the affected shared components (e.g., AutoCAD, Fusion 360, or other design products)
  2. Obtain the 2026.5 or later release of the affected Autodesk product from the official Autodesk website or your software distribution channel
  3. Uninstall the current version of the Autodesk product
  4. Install the version 2026.5 or later that includes the fixed shared components
  5. Verify the installation was successful by checking the product version information
  6. Test that SLDPRT files can be opened and parsed without issues in the updated version
Caveat Review Autodesk's release notes for 2026.5 for any feature changes, deprecated functionality, or workflow modifications that may affect your projects

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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