dbcve.org
Shared ComponentsApplication · Autodesk

CVE-2025-14593

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 CATPART 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

This is an out-of-bounds read vulnerability in how certain Autodesk products parse CATPART files. When parsing a maliciously crafted CATPART file, the parser reads memory outside the intended buffer boundaries, potentially exposing sensitive data or enabling arbitrary code execution in the current process context.

MitigationDo not open untrusted CATPART files in Autodesk products. Apply vendor patches when released and monitor security advisories for affected products.

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 Shared Components version
    Check the version of Autodesk Shared Components installed on the system. This is typically found in the program's About or Help section, or via the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\SharedComponents (or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Autodesk\SharedComponents for 32-bit on 64-bit systems). Look for a Version or InstalledVersion value.
    Affected if The installed version is lower than 2026.5 (for example, 2026.4, 2025.x, or earlier releases).
  2. Verify CATPART file handling capability
    Check whether the Autodesk installation includes components for handling CATPART files. Look for CATIA or CATPART-related DLLs or modules in the installation directory (commonly in a Shared Components or Plug-ins subfolder).
    Affected if CATPART parsing modules are present and loaded by the application.
  3. Confirm product usage of vulnerable parser
    Determine if any installed Autodesk product loads the CATPART parser module (typically a DLL with 'CAT' or 'CATIA' in the name within the Shared Components path). Check product documentation or run the application with process monitoring tools to observe loaded modules.
    Affected if The application loads a CATPART parsing DLL from an affected version of Autodesk Shared Components.

A user is affected if their installed Autodesk Shared Components version is below 2026.5 AND they have CATPART file handling capability enabled or present in their installation.

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

Do not open untrusted CATPART files in Autodesk products. Apply vendor patches when released and monitor security advisories for affected products.

Recommended fix Moderate confidence

Shared Components version 2026.5 or later (bundled with corresponding Autodesk product releases)

  1. Identify the Autodesk product(s) in your environment that use the Shared Components for parsing CATPART files
  2. Locate the specific Autodesk product version and its associated Shared Components version
  3. Upgrade the affected Autodesk product to a version that includes Shared Components version 2026.5 or later
  4. Verify the upgrade by checking the product's About/Info section to confirm the Shared Components version is 2026.5 or higher
  5. Test that CATPART files can be opened normally in the updated version

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
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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