dbcve.org
Shared ComponentsApplication · Autodesk

CVE-2025-10899

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

A maliciously crafted MODEL file parsed by certain Autodesk products triggers an out-of-bounds memory write vulnerability. This memory corruption can allow an attacker to crash the application, corrupt data, or execute arbitrary code within the application's security context.

MitigationApply vendor-supplied patches from Autodesk when available. Until then, restrict the intake of MODEL files from untrusted sources and implement file validation at entry points to reject abnormally structured files.

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 Shared Components version
    Locate the Autodesk Shared Components installation directory and check the version information in the product's About or version details. This is typically found in the application's help menu or the installation folder's version resource.
    Affected if The installed version is lower than 2026.5
  2. Determine if MODEL file parsing is in use
    Check whether the Autodesk application has recent activity or logs showing import or processing of MODEL files. Look for file extension handlers registered for .model files or recent file history in the application.
    Affected if MODEL files are being opened or processed by the application
  3. Inspect application file handling configuration
    Review the application's file type associations and import settings to confirm .model files are registered as supported file types that can be opened directly.
    Affected if .model files are associated as openable file types in the application
  4. Check for file intake controls
    Examine whether there are application settings, group policies, or security tools that restrict or validate incoming MODEL files from external or untrusted sources.
    Affected if No file validation or intake restrictions are configured for MODEL files

You are affected if Autodesk Shared Components version is below 2026.5 AND the application processes MODEL files from potentially 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-supplied patches from Autodesk when available. Until then, restrict the intake of MODEL files from untrusted sources and implement file validation at entry points to reject abnormally structured files.

Recommended fix Moderate confidence

2026.5

  1. Identify all installed Autodesk products that use the affected Shared Components (any version before 2026.5)
  2. Download Autodesk products version 2026.5 or later from the official Autodesk website (www.autodesk.com)
  3. Uninstall all previous versions of the affected Autodesk products
  4. Install the updated version 2026.5 or later which includes the fixed Shared Components
  5. Verify the installation by checking that Shared Components version is 2026.5 or later

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-2025-10899 — 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-10899 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