dbcve.org
Shared ComponentsApplication · Autodesk

CVE-2025-10881

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 a Heap-Based Overflow 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 heap-based buffer overflow vulnerability exists in certain Autodesk products when parsing CATPRODUCT files. A specially crafted malicious CATPRODUCT file can trigger heap corruption, potentially allowing an attacker to cause a denial of service, read sensitive data from memory, or execute arbitrary code in the context of the current process.

MitigationApply vendor patches from Autodesk when available. Avoid opening CATPRODUCT files from untrusted or unknown sources until patches are applied.

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 software by looking in common installation directories (C:\Program Files\Autodesk or C:\Program Files (x86)\Autodesk) and reviewing installed programs via Windows Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or using 'Get-ItemProperty' PowerShell command for registered applications
    Affected if Any Autodesk product is installed and the Autodesk Shared Components version is below 2026.5
  2. Determine Autodesk Shared Components version
    Locate the Autodesk Shared Components installation directory, typically found under the Autodesk product folder (e.g., C:\Program Files\Autodesk\Shared), then right-click the main executable or DLL file (commonly acmpay.dll, AdAppManager.exe, or files in a 'Common' subfolder) and view Properties > Details to find the File Version, or use PowerShell: Get-Item 'C:\Program Files\Autodesk\Shared\*' | Select-Object Name, VersionInfo
    Affected if The installed version is below 2026.5 (e.g., 2026.4, 2025.x, or earlier)
  3. Check for CATPRODUCT file handling capability
    Review installed file type associations and plugins: Open Windows Registry at HKCR\.catproduct and HKCR\CATPRODUCT to see if CATPRODUCT files are registered as handled by Autodesk software, or check the application's plugin/config directory for CATPRODUCT-related import/export modules
    Affected if CATPRODUCT file association or import module exists, indicating the product can parse CATPRODUCT files
  4. Verify if CATPRODUCT parsing is enabled in application settings
    Open the Autodesk application (e.g., AutoCAD, Inventor, or Fusion 360), navigate to Options or Preferences > File Types or Import/Export settings, and check whether CATPRODUCT is listed as an enabled or available import format
    Affected if CATPRODUCT is listed as an enabled or available import format in the application settings

The environment is vulnerable if any Autodesk product is installed with Autodesk Shared Components version below 2026.5 AND CATPRODUCT file parsing capability is enabled or available in the software.

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 patches from Autodesk when available. Avoid opening CATPRODUCT files from untrusted or unknown sources until patches are applied.

Recommended fix High confidence

2026.5 or later

  1. Identify all Autodesk products installed that utilize the affected shared components for parsing CATPRODUCT files
  2. Access the official Autodesk support or download portal at www.autodesk.com
  3. Locate and download the 2026.5 or later version of the affected Autodesk product(s)
  4. Close any running Autodesk applications
  5. Run the installer for version 2026.5 or later to update the software
  6. Restart the system if prompted by the installer
  7. Verify that the installed version is 2026.5 or later by checking the application's About/Help section

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

Fix this in Shared Components Scoped from the published advisory
  • Consultation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $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 $1,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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