dbcve.org
Shared ComponentsApplication · Autodesk

CVE-2025-9452

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 arbitrary code execution in the context of the current process due to improper memory handling during file parsing.

MitigationApply available vendor patches for affected Autodesk products. Until patches are available, exercise caution when opening SLDPRT files from untrusted sources and consider disabling file preview features.

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 Autodesk products that handle SLDPRT files
    Check installed programs for Autodesk applications such as AutoCAD, DesignReview, or other products that commonly open SLDPRT files. Use 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' or review Programs and Features.
    Affected if Any Autodesk product that opens SLDPRT files is installed
  2. Determine Autodesk Shared Components version
    Locate and check the version of Autodesk Shared Components (ACCoreComponents, ACForceCore, or similar runtime components). Look in the application's installation directory or check assembly version info. Common locations include Program Files\Autodesk or within the specific product's folder.
    Affected if Shared Components version is displayed as anything less than 2026.5 or the version cannot be determined as 2026.5 or higher
  3. Verify SLDPRT file association exists
    Check if .sldPRT file extension is associated with any installed Autodesk application. Use 'assoc .sldPRT' or check registry under HKCR\.sldPRT to see the associated handler.
    Affected if SLDPRT files are associated with an installed Autodesk application
  4. Confirm file preview or thumbnail handler is enabled
    Check if Windows thumbnail preview or file preview handler is enabled for SLDPRT files. Inspect registry under HKCR\.sldPRT\ShellEx\{ThumbnailHandler...} or check if preview pane in Windows Explorer loads thumbnails for these files.
    Affected if Preview features for SLDPRT files are enabled in the Windows shell

You are affected if an installed Autodesk product uses Shared Components version below 2026.5 and the system can open or preview 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

Apply available vendor patches for affected Autodesk products. Until patches are available, exercise caution when opening SLDPRT files from untrusted sources and consider disabling file preview features.

Recommended fix High confidence

2026.5 or later

  1. Identify all Autodesk products installed that utilize the Shared Components (this includes design and CAD applications that process SLDPRT files)
  2. Check the current version of each installed Autodesk product
  3. Download Autodesk product updates from the official Autodesk website (www.autodesk.com) or through your organization's software distribution system
  4. Upgrade all affected Autodesk products to version 2026.5 or later
  5. Verify the upgrade was successful by checking the product version number
  6. After upgrading, do not open untrusted or unexpected SLDPRT files in any Autodesk product

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

Fix this in Shared Components Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
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,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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