dbcve.org
Shared ComponentsApplication · Autodesk

CVE-2026-0874

HIGH · 7.8 CVSS v3.1 Published 2026-02-18
Fix available
A fix is available. Upgrade to 2026.6 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 Write vulnerability. A malicious actor may leverage this vulnerability to cause a crash, cause data corruption, 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

An out-of-bounds write vulnerability exists in certain Autodesk products when parsing maliciously crafted CATPART files. The vulnerability allows memory corruption that can be leveraged by an attacker to crash the application, corrupt data, or execute arbitrary code in the current process context.

MitigationAvoid opening CATPART files from untrusted or unknown sources. Implement file type validation and sandboxing for Autodesk product file imports until an official vendor patch is available.

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.6

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 using shared components
    Locate installed Autodesk applications on the system that handle CAD file imports, particularly those capable of opening CATPART files
    Affected if Any Autodesk product that imports CATPART files is present on the system
  2. Locate Autodesk Shared Components version
    Access the installed Autodesk product information or shared component library and retrieve the version number of Autodesk Shared Components
    Affected if Unable to determine the version or version information is missing
  3. Compare version against affected range
    Check if the installed Autodesk Shared Components version is below 2026.6
    Affected if Installed version is less than 2026.6 (for example, 2026.5, 2025.x, or earlier)
  4. Assess CATPART file handling exposure
    Determine whether the installed Autodesk products have the capability to open or import CATPART files, which is the attack vector for this vulnerability
    Affected if The product can parse CATPART files and the version is below 2026.6

The environment is affected if Autodesk Shared Components version is below 2026.6 and any installed Autodesk product can open CATPART 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.6 or later
Fixed in 2026.6
Interim mitigation

Avoid opening CATPART files from untrusted or unknown sources. Implement file type validation and sandboxing for Autodesk product file imports until an official vendor patch is available.

Recommended fix High confidence

2026.6 or later

  1. Identify all Autodesk products installed that handle CATPART files (e.g., AutoCAD, Inventor, or other CAD applications using Shared Components
  2. Verify the current version of the installed Autodesk software by checking 'About' or the application help section
  3. Download Autodesk version 2026.6 or later from the official Autodesk website (www.autodesk.com) or your organization's software distribution point
  4. Close all running Autodesk applications
  5. Install the updated version following Autodesk's standard installation procedure
  6. Restart the system if prompted by the installer
  7. Verify the installed version is 2026.6 or higher to confirm the patch was applied
Caveat Review Autodesk release notes for version 2026.6 to check for any breaking changes in file format support or workflow modifications that may affect existing projects

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-2026-0874 — 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-2026-0874 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