Skip to main content

Autodesk Shared Components CVE-2025-10888

HIGH
Out-of-bounds Write (CWE-787)
2025-12-16 psirt@autodesk.com
7.8
CVSS 3.1 · Vendor: autodesk
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Deliver crafted MODEL file to user
  2. Exploit
    Victim opens file in Autodesk product
  3. Execution
    Trigger out-of-bounds write in parser
  4. Impact
    Execute code as current user

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an attacker to deliver a specially crafted MODEL file AND a victim to open/parse that file in an affected Autodesk product that uses the vulnerable shared components (the advisory ADSK-SA-2025-0024 should be consulted for the exact product list). The vulnerability is not remotely triggerable over a network and cannot self-propagate: the mandatory user interaction (UI:R) of opening the malicious file, combined with the local attack vector (AV:L), is the primary limiting factor. There is no privilege prerequisite on the target system, but code executes only in the context of the current user running the application, not with elevated privileges.

Impact

This is a genuine but conditional priority. The CVSS 3.1 base score of 7.8 (High) is driven by full CIA impact (C:H/I:H/A:H) reflecting potential arbitrary code execution, but the vector tempers real-world urgency: AV:L means there is no network attack surface, and UI:R means a user must actively open a maliciously crafted MODEL file for exploitation to occur. PR:N (unauthenticated) is somewhat misleading here - no credentials are needed, but the attacker instead relies on social engineering to deliver the file. No EPSS score, KEV listing, or POC indicator was supplied in the input, so there is no signal of active exploitation or published exploit code; this is consistent with a vendor-self-reported (Autodesk PSIRT) memory-corruption bug rather than a mass-exploited flaw. SSVC-style reading: exploitation status appears to be 'none', automatability is low (requires user interaction, not autonomously scalable), and technical impact is total. Net: a credible local/client-side code-execution risk warranting prompt patching in Autodesk-heavy environments, but not an emergency on par with a remotely exploitable, actively-exploited bug. No conflicting signals were detected between the CVSS vector and the description - both consistently describe local file-parsing exploitation.

Exploit ScenarioDerived

An attacker crafts a malicious MODEL file and delivers it to a victim via email, a shared project repository, or a download, relying on the fact that CAD/design users routinely open third-party model files. When the victim opens the file in a vulnerable Autodesk product, the parser performs an out-of-bounds write that corrupts memory, allowing the attacker to crash the application, corrupt data, or execute code in the context of the current user. No public exploit code is identified in the provided data.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 07, 2026

An out-of-bounds write (CWE-787) in Autodesk Shared Components (CVE-2025-10888, CVSS 7.8) can be triggered when an affected Autodesk product parses a maliciously crafted MODEL file, producing memory corruption that can crash the application, corrupt data, or execute arbitrary code in the context of the user running the application. Per the CVSS vector (AV:L/AC:L/PR:N/UI:R), exploitation is local and unauthenticated but requires the victim to open or parse the malicious file, so it is not remotely triggerable and cannot self-propagate; code execution is confined to the current user's privileges, not elevated rights. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing); the vendor advisory ADSK-SA-2025-0024 should be consulted for the definitive list of affected products and available fixes.

RemediationAI

The primary action is to apply the fix identified in Autodesk security advisory ADSK-SA-2025-0024 (https://www.autodesk.com/trust/security-advisories/adsk-sa-2025-0024); the available input data does not specify an exact patched version number, so the advisory must be consulted for the precise fixed release and for the product list, and no version number should be assumed from the wildcard CPE. Until patched builds are deployed, apply compensating controls that target the file-delivery step, since exploitation requires a user to open a malicious MODEL file: block or quarantine inbound MODEL attachments and downloads at the mail gateway, web proxy, and endpoint DLP layers, and restrict MODEL file handling to trusted internal sources (trade-off: legitimate engineering workflows that exchange MODEL files with partners or customers will require an exception or a sanitization/scanning step). Consider application allow-listing or controlled execution for Autodesk products and keep OS-level mitigations such as ASLR and DEP enabled to complicate any memory-corruption exploitation (trade-off: application compatibility testing may be needed). Users who must open untrusted MODEL files can be directed to do so in a disposable, non-privileged virtual machine or sandbox without access to production shares (trade-off: heavier workflow overhead). Monitor for suspicious crashes of Autodesk processes and for child processes spawned from them, which may indicate exploitation attempts.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is an out-of-bounds write (CWE-787), a memory-safety class in which a program writes past the end of an allocated buffer while parsing attacker-controlled input. Here the input is a MODEL file consumed by Autodesk Shared Components, a common library set reused across multiple Autodesk applications (CPE cpe:2.3:a:autodesk:shared_components:* with a wildcard version, indicating the flaw is not tied to a single tagged release). Because the vulnerable code lives in a shared parsing component rather than in one product, any Autodesk application that loads MODEL files through these components may be exposed, which is why the vendor advisory's product list is authoritative. Successful corruption of heap or stack structures during parsing can lead to a crash (denial of service), silent data corruption, or control-flow hijacking that yields code execution in the context of the process opening the file. The attack surface is a file-parsing boundary: the attacker must first deliver a crafted MODEL file and then convince a user to open it in an affected application (AV:L, UI:R, PR:N), so the practical barrier to exploitation is social engineering rather than network reachability, and standard OS mitigations (ASLR, DEP) raise the effort required to convert the memory-corruption primitive into reliable code execution.

Know when Shared Components gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (autodesk) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 7.8 HIGH

File must be opened locally by a user so AV:L and UI:R; no auth needed (PR:N); out-of-bounds write enables code execution with full CIA impact in-process.

3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (autodesk).

CVSS VectorVendor: autodesk

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

Autodesk Shared Components contains a high-severity out-of-bounds write vulnerability (CVE-2025-10888) that can be triggered when a user opens a maliciously crafted MODEL file, potentially leading to code execution with the user's privileges. While no public exploit identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing), the lack of a vendor-released patch identified at time of analysis and the reliance on user interaction with untrusted files pose a risk to organizations whose employees regularly handle such files. Leadership should prioritize identifying affected products via Autodesk's advisory and implementing interim controls to mitigate potential data corruption or system compromise.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include: restricting the opening of untrusted MODEL files, enforcing least privilege, using application sandboxing or isolation, and monitoring for unexpected application crashes or memory corruption events.

Threat Intelligence Overview

EPSS Score
0.3%
Top 84% exploitable
Prevalence
Medium
Autodesk shared components used across common but industry-specific CAD/design software
Data Quality
2 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
High

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

Affected Products (CPE)CVE.org

cpe:2.3:a:autodesk:shared_components:*:*:*:*:*:*:*:*
CVE-2025-10881 HIGH
7.8 Dec 16

Heap-based buffer overflow in Autodesk Shared Components - the shared file-parsing libraries used by multiple Autodesk a

CVE-2025-10898 HIGH
7.8 Dec 16

Out-of-bounds write in Autodesk Shared Components allows local attackers to execute arbitrary code in the context of the

CVE-2025-10889 HIGH
7.8 Dec 16

Memory corruption in the Autodesk Shared Components parser that handles CATPART files lets an attacker execute arbitrary

CVE-2026-0875 HIGH
7.8 Feb 18

Out-of-bounds write in Autodesk shared components allows local attackers to execute arbitrary code, corrupt data, or cra

CVE-2026-0874 HIGH
7.8 Feb 18

Out-of-bounds write in Autodesk products' CATPART file parser enables local attackers to achieve arbitrary code executio

CVE-2025-8892 HIGH
7.8 Sep 22

A maliciously crafted PRT file, when parsed through certain Autodesk products, can force a Memory Corruption vulnerabili

CVE-2025-9458 HIGH
7.8 Nov 07

A maliciously crafted PRT file, when parsed through certain Autodesk products, can force a Memory Corruption vulnerabili

CVE-2025-9460 HIGH
7.8 Dec 16

An out-of-bounds read in Autodesk Shared Components can be triggered when a user opens or imports a maliciously crafted

CVE-2025-9459 HIGH
7.8 Dec 16

An out-of-bounds read in Autodesk shared components lets an attacker crash an affected Autodesk application, read memory

CVE-2025-9457 HIGH
7.8 Dec 16

Memory corruption in Autodesk Shared Components allows an attacker to execute arbitrary code in the context of the curre

CVE-2025-9456 HIGH
7.8 Dec 16

Memory corruption in Autodesk Shared Components allows arbitrary code execution when a user opens a maliciously crafted

CVE-2025-9455 HIGH
7.8 Dec 16

Parsing a maliciously crafted CATPRODUCT (CATIA assembly) file in Autodesk products that rely on the affected shared com

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy