CVE-2025-10889
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 · uneditedA maliciously crafted CATPART 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 confidenceA memory corruption vulnerability exists in certain Autodesk products when parsing maliciously crafted CATPART files. The specially crafted file triggers memory corruption during parsing, which can be leveraged by an attacker to achieve arbitrary code execution within the context of the current process.
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< 2026.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Autodesk productsCheck Program Files/Program Files (x86) for Autodesk folders, or review installed programs list in Windows Settings/Control PanelAffected if Any Autodesk product is installed that uses the shared components
-
Locate Autodesk Shared Components versionCheck the version of ACShared.dll or similar shared library files in the Autodesk installation directory, typically found in the main Autodesk program folder or Common Files folderAffected if The version number is lower than 2026.5 (or the file lacks a visible version attribute indicating it's pre-2026.5)
-
Determine CATPART file handlingSearch for CATPART file associations or review if the system has software that opens .catpart extension files (common with CATIA or Autodesk products that handle CAD data)Affected if The system has associations or software configured to open CATPART files
You are affected if you have any Autodesk product installed with Autodesk Shared Components version prior to 2026.5 and the system is configured to open or process CATPART files.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2026.5
Apply the vendor-supplied patch or update to the affected Autodesk product when available. Avoid opening CATPART files from untrusted sources, and consider running affected applications with reduced privileges to limit the impact of potential code execution.
2026.5
- Identify all Autodesk products installed that use the affected shared components (CATPART file parsing functionality)
- Obtain Autodesk AutoCAD 2026.5 or later version from the official Autodesk website or your organization's software distribution channel
- Uninstall the current version of the affected Autodesk product
- Install the updated version (2026.5 or later)
- Verify the installation completed successfully
- Test that CATPART files can be opened and parsed without issues
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10889 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10889 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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