dbcve.org
Shared ComponentsApplication · Autodesk

CVE-2025-10900

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
AA maliciously crafted MODEL 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 specially crafted MODEL files. The vulnerability allows a malicious actor to overwrite memory outside allocated buffers by providing a specially crafted file, potentially leading to arbitrary code execution in the context of the current process.

MitigationApply vendor patches from Autodesk for affected products. Until patches are available, implement file validation and sandboxing for untrusted MODEL files, and restrict file handling privileges where possible.

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 Autodesk product installations
    Check installed Autodesk products on the system. Look for applications that include Autodesk Shared Components (common locations: C:\Program Files\Autodesk\ or C:\Program Files (x86)\Autodesk\). Use 'Programs and Features' in Control Panel or run 'Get-ItemProperty' in PowerShell for installed software.
    Affected if Any Autodesk product with Shared Components version lower than 2026.5 is installed on the system
  2. Determine Autodesk Shared Components version
    Locate the Autodesk Shared Components installation directory. Check the version of the affected DLL or executable component. This is typically found in the product's main installation folder under a 'Bin' or 'Common' subdirectory. Right-click the file, select Properties, and examine the 'Details' tab for version information.
    Affected if The Shared Components version shown is below 2026.5 (for example, 2026.4, 2025.x, or earlier)
  3. Verify MODEL file parsing capability
    Check if the installed Autodesk product has the ability to open or import MODEL files. Look for file association handlers for .model extensions, or check application log files that indicate MODEL file processing capability. This can also be confirmed by searching for 'model' in the application's import/export or file type support documentation.
    Affected if The Autodesk product supports opening, importing, or rendering MODEL files, enabling the vulnerable parsing code path
  4. Assess exposure to untrusted MODEL files
    Examine file handling workflows to determine if the system processes MODEL files from external or untrusted sources. Check for directories where MODEL files are stored, email attachments, downloaded files, or network shares that could contain specially crafted files. Review any automated processing rules.
    Affected if Users can open or the system automatically processes MODEL files from untrusted or external sources without prior validation

The environment is affected if an Autodesk product with Shared Components version below 2026.5 is installed and the system can parse MODEL files, especially 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

Apply vendor patches from Autodesk for affected products. Until patches are available, implement file validation and sandboxing for untrusted MODEL files, and restrict file handling privileges where possible.

Recommended fix Moderate confidence

2026.5

  1. Identify all Autodesk products installed that use the affected shared components (e.g., AutoCAD, Revit, Fusion 360, or other products that process MODEL files)
  2. Check the current version of the shared components or the Autodesk product itself
  3. Navigate to the official Autodesk support or download page at www.autodesk.com
  4. Download the updated version 2026.5 or later of the affected Autodesk product
  5. Follow Autodesk's standard installation and update procedures to apply the patch
  6. Restart the application if required after the update
  7. Verify the version has been updated to 2026.5 or later
Caveat Standard Autodesk upgrade considerations apply - review release notes for any workflow or compatibility changes

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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