dbcve.org
Shared ComponentsApplication · Autodesk

CVE-2025-10882

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 X_T 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 X_T file parsed by certain 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 patches or updates to affected Autodesk products; avoid opening X_T files from untrusted sources until patches are applied.

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
    Check Windows Programs and Features (appwiz.cpl), macOS Applications folder, or Linux package manager for Autodesk software installations such as AutoCAD, Revit, Fusion 360, or other Autodesk applications that use X_T file handling.
    Affected if Any Autodesk product that handles X_T files is installed on the system
  2. Determine Autodesk Shared Components version
    Locate the Autodesk Shared Components installation folder (commonly in Program Files/Autodesk or Application Support), then check the version of the core component DLLs (often named something like AutodeskSharedComponents.dll or within a version-specific folder). Right-click the DLL, select Properties, and examine the File Version field.
    Affected if The Shared Components version is below 2026.5 (e.g., 2026.0 through 2026.4, or any version shown as earlier than 2026.5)
  3. Confirm X_T file handler is present
    Search the Autodesk installation directory for file type handlers related to X_T parsing, typically identified by searching for files with 'xt' or 'x_t' in the filename, or check the file association configuration in the Windows Registry under HKCR\.x_t or within the Autodesk product's configuration files.
    Affected if The X_T file handler or parser module exists on the system, indicating the vulnerable code path is present
  4. Check for recent X_T file processing activity
    Review the application event logs (Windows Event Viewer > Application logs), Autodesk product logs, or filesystem access timestamps on the Autodesk program directory to identify recent X_T file loading events.
    Affected if X_T files have been opened or processed by the Autodesk product, demonstrating the attack surface is active

A system is affected if it has any Autodesk product installed that uses Autodesk Shared Components version lower than 2026.5 and has the capability to parse X_T files, especially if users open X_T 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 patches or updates to affected Autodesk products; avoid opening X_T files from untrusted sources until patches are applied.

Recommended fix Moderate confidence

Upgrade to Autodesk products with Shared Components version 2026.5 or later

  1. 1. Identify all Autodesk products installed that use the affected Shared Components (this vulnerability affects multiple Autodesk applications that share common parsing libraries)
  2. 2. Visit the official Autodesk support or security advisory page at www.autodesk.com to locate the security update for CVE-2025-10882
  3. 3. Download the updated version of your Autodesk product(s) that includes Shared Components version 2026.5 or later
  4. 4. Close all Autodesk applications and any related background processes
  5. 5. Run the installer/auto-update to apply the patched version
  6. 6. Verify the installed Shared Components version is 2026.5 or later by checking the About/Support information within the application
Caveat Autodesk minor version updates typically maintain backward compatibility for file formats, but review release notes for any specific functionality changes in the 2026.5 release

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
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,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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