dbcve.org
Shared ComponentsApplication · Autodesk

CVE-2025-9455

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 CATPRODUCT 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 · high confidence

A maliciously crafted CATPRODUCT file parsed by certain Autodesk products triggers an Out-of-Bounds Read vulnerability, allowing a local attacker to potentially read sensitive memory, cause a denial of service (crash), or achieve arbitrary code execution within the context of the user's current process.

MitigationApply vendor-supplied patches for affected Autodesk products; until patches are available, exercise extreme caution when opening CATPRODUCT 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 installed Autodesk products
    Open Windows Control Panel > Programs and Features, or use 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' to list installed software. Look for any Autodesk applications.
    Affected if Any Autodesk product is installed on the system.
  2. Determine Autodesk Shared Components version
    Check the version of the Autodesk Shared Components by locating the main Autodesk component DLL or executable. Common locations include: C:\Program Files\Autodesk\ or %PROGRAMDATA%\Autodesk\. Look for files named SharedComponents.dll, AdApplicationFrame.dll, or similar core components, then right-click > Properties > Details to view the File Version.
    Affected if The detected version of Autodesk Shared Components is earlier than 2026.5 (e.g., 2026.0, 2025.x, etc.).
  3. Confirm CATPRODUCT file handling is present
    Verify the installation includes modules that handle CATPRODUCT files (Creo/CATIA product files). Check for presence of translation or import modules within the Autodesk installation directory that process these file types.
    Affected if CATPRODUCT file import/translation functionality exists in the installed Autodesk software.
  4. Review recent CATPRODUCT file activity (optional)
    Check Windows Event Viewer or antivirus logs for any recent attempts to open or process CATPRODUCT files from untrusted or unknown sources.
    Affected if CATPRODUCT files from untrusted sources have been opened recently on the system.

You are affected if any Autodesk product is installed with Autodesk Shared Components version earlier than 2026.5 and the software processes CATPRODUCT 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-supplied patches for affected Autodesk products; until patches are available, exercise extreme caution when opening CATPRODUCT files from untrusted sources and consider disabling file preview features.

Recommended fix High confidence

2026.5

  1. Identify which Autodesk products are installed that use the shared components (products that can open CATPRODUCT files)
  2. Check current version of each affected product in Help > About or by running the product
  3. Download Autodesk version 2026.5 or later from the official Autodesk website (autodesk.com) or your Autodesk Account
  4. Close all Autodesk applications running on the system
  5. Run the installer for the new version and follow the installation prompts
  6. After installation, verify the version shows 2026.5 or later in Help > About
  7. Test that CATPRODUCT files open correctly in the updated application
Caveat Version upgrades may introduce changes to file compatibility, UI, or workflow; review Autodesk release notes 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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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