dbcve.org
Shared ComponentsApplication · Autodesk

CVE-2025-10887

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 MODEL 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 confidence

A memory corruption vulnerability exists in certain Autodesk products when parsing maliciously crafted MODEL files. The vulnerability allows an attacker to execute arbitrary code within the context of the current process by leveraging the memory corruption triggered during file parsing.

MitigationAvoid opening MODEL files from untrusted sources until Autodesk releases and applies the corresponding security update. Implement network segmentation and endpoint protection to reduce exposure to file-based attacks.

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 Programs and Features (Windows) or check /Applications (macOS) for any Autodesk software such as AutoCAD, Revit, Maya, 3ds Max, or other Autodesk applications
    Affected if Any Autodesk product is installed that relies on Autodesk Shared Components for file parsing
  2. Locate Autodesk Shared Components version
    Check the installed version of Autodesk Shared Components by examining the program's version information in the software's About dialog or in the installation directory's version resource
    Affected if The installed version is lower than 2026.5 (any version before 2026.5 is affected)
  3. Confirm MODEL file parsing capability
    Verify that the installed Autodesk product can open or import MODEL files - this is typically a native capability of CAD/design software
    Affected if The software can parse MODEL files (this is the default behavior for affected products)
  4. Check for recent MODEL file activity
    Review the system for recently opened MODEL files, particularly from untrusted or external sources, by checking recent documents or file access logs
    Affected if MODEL files from untrusted sources have been opened on the system

The environment is affected if any Autodesk product using Autodesk Shared Components version below 2026.5 is installed and can process MODEL files, especially if users open files from untrusted sources.

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

Avoid opening MODEL files from untrusted sources until Autodesk releases and applies the corresponding security update. Implement network segmentation and endpoint protection to reduce exposure to file-based attacks.

Recommended fix Moderate confidence

2026.5 or later

  1. Identify the specific Autodesk product(s) in use that utilize the affected shared components
  2. Determine the current version of the Autodesk software (typically found in Help > About or the application's info dialog)
  3. Verify the installed version is below 2026.5
  4. Obtain the updated version 2026.5 or later from the official Autodesk website or your software distribution channel
  5. Create a backup of any important project files and settings before upgrading
  6. Uninstall the current Autodesk product or use the installer's update function
  7. Install the version 2026.5 or newer which contains the fixed shared components
  8. Verify the installation completed successfully and the version now shows 2026.5 or later
Caveat Autodesk version upgrades may include feature changes; review release notes for the specific product before upgrading

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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