dbcve.org
Shared ComponentsApplication · Autodesk

CVE-2025-10898

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 · high confidence

A maliciously crafted MODEL file parsed by affected Autodesk products triggers an out-of-bounds write vulnerability, allowing an attacker to crash the application, corrupt data, or execute arbitrary code within the current process context.

MitigationApply vendor-supplied security patches for affected Autodesk products. Until patched, avoid opening MODEL files from untrusted sources.

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 Windows Control Panel > Programs and Features, or use PowerShell: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion | Where-Object {$_.DisplayName -like '*Autodesk*'}
    Affected if Any Autodesk product is installed on the system
  2. Locate Autodesk Shared Components version
    Check the version of the SharedComponents folder or DLLs. Common paths: C:\Program Files\Autodesk\SharedComponents\ or C:\Program Files (x86)\Autodesk\SharedComponents\. Right-click the main DLL (e.g., Autodesk.SharedComponents.dll) and select Properties > Details to view the File Version.
    Affected if The Shared Components version shown is lower than 2026.5
  3. Confirm MODEL file parsing capability
    Check if the installed Autodesk product can open or import MODEL files. Look for MODEL file type associations in the application (File > Open, File > Import) or search for .model file extensions in recent Autodesk project folders.
    Affected if The product is configured to parse or import MODEL files from external sources
  4. Verify patch status
    In the Autodesk desktop app or via Help > Check for Updates, confirm whether security updates are available. Alternatively, cross-reference the installed build number with Autodesk security advisory references for CVE-2025-10898.
    Affected if No security patch for CVE-2025-10898 has been applied and the version remains below 2026.5

A user is affected if Autodesk Shared Components version is below 2026.5 and the product is capable of parsing MODEL files from external or 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 security patches for affected Autodesk products. Until patched, avoid opening MODEL files from untrusted sources.

Recommended fix Moderate confidence

2026.5

  1. Identify Autodesk products installed that rely on the affected shared components (this vulnerability may impact multiple Autodesk applications)
  2. Back up any critical project files, preferences, and custom configurations
  3. Navigate to Autodesk's official support or download page at www.autodesk.com
  4. Locate and download the 2026.5 or later version of the affected Autodesk product(s)
  5. Run the installer and follow the on-screen prompts to complete the upgrade
  6. After installation, verify the version by checking Help > About or the application info panel to confirm version 2026.5 or later is installed
  7. Re-test any workflow with MODEL files to confirm normal operation
Caveat Review Autodesk's release notes for version 2026.5 for any workflow, file format, or API changes 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
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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