Autodesk Shared Components CVE-2025-10900
HIGHAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted MODEL file to victim
-
DeliveryVictim opens file in Autodesk product
-
ExploitTrigger out-of-bounds write in parser
-
ExecutionCorrupt process memory
-
ImpactExecute 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 a victim to open a maliciously crafted MODEL file in an affected Autodesk product that uses the vulnerable shared components (per CPE cpe:2.3:a:autodesk:shared_components). The limiting factors are significant: the CVSS vector is AV:L with UI:R, so there is no remote or automated trigger - the attacker cannot reach the parser without first delivering the file and convincing the user to open it. No authentication is needed on the target (PR:N), and code runs only in the context of the current user (S:U), not elevated. This is a file-format parsing flaw, so risk is confined to users who process untrusted MODEL files. |
| Impact | The CVSS 3.1 base score is 7.8 (High) driven by full C/I/A impact, but the vector tells a more constrained story: AV:L and UI:R mean this is NOT remotely triggerable - an attacker must get a victim to open a maliciously crafted MODEL file locally. PR:N and AC:L lower the bar once the file reaches the target, so the practical risk is a classic 'open a weaponized file' social-engineering chain rather than wormable remote exploitation. No EPSS score, CISA KEV listing, or public POC was provided in the input, so there is no evidence of active exploitation or available exploit code at time of analysis. The arbitrary-code-execution outcome is the worst case; the vendor description also lists crash and data corruption as more likely practical results, which is typical of memory-corruption bugs where reliable RCE requires defeating modern mitigations. Net: a legitimate patch-worthy High, but it is a user-interaction-gated local file-parsing issue, not a drop-everything remote threat. No conflicting signals in the data itself; the main limitation is the absence of exploitation-probability telemetry (EPSS/KEV/POC all absent). |
| 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 victim opening it in a vulnerable Autodesk product. Parsing the file triggers an out-of-bounds write (CWE-787) that corrupts memory, causing a crash or, in the best case for the attacker, code execution in the context of the current user. No public exploit code was identified at time of analysis, so weaponization would require original exploit development. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
An out-of-bounds write in Autodesk Shared Components lets a maliciously crafted MODEL file corrupt memory and potentially achieve arbitrary code execution in the context of the current process when parsed by an affected Autodesk product. Exploitation requires the victim to open the crafted file locally (CVSS AV:L/UI:R, PR:N), so it is not remotely or automatically triggerable; no authentication is required on the target and impact is not elevated beyond the current user (S:U). Scoring is 7.8 (High) with full confidentiality, integrity, and availability impact, and no public exploit code or confirmed in-the-wild activity was identified at time of analysis.
RemediationAI
No fixed version is confirmed in the available data; the authoritative source for patched builds is Autodesk security advisory ADSK-SA-2025-0024 (https://www.autodesk.com/trust/security-advisories/adsk-sa-2025-0024), so administrators should check that advisory and apply the listed product updates as soon as they are published. Until then, the practical compensating controls target the delivery vector rather than the parser: strip or quarantine .MODEL attachments at email and web gateways so untrusted files never reach user desktops, and block direct download of MODEL files from untrusted sources via proxy/content filtering - the trade-off is that legitimate data-exchange workflows using MODEL files must be routed through a vetted channel. Enforce Mark-of-the-Web/Protected View-style handling and disable automatic file preview or thumbnail generation for MODEL files so the parser is not invoked without an explicit user action, at the cost of some workflow convenience. Because the vector is AV:L/UI:R with S:U scope, running affected applications as unprivileged, non-administrative users and confining MODEL parsing to a sandboxed VM or isolated workstation meaningfully bounds the blast radius, though it does not prevent the crash or in-process code execution itself. User awareness training to avoid opening MODEL files from unknown senders is a low-cost supplement but should not be relied on as the primary control.
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 flaw is a classic memory-safety failure (CWE-787, out-of-bounds write) inside Autodesk's shared components library, which is consumed by multiple Autodesk desktop applications rather than a single product - reflected in the CPE cpe:2.3:a:autodesk:shared_components with a wildcard version, indicating the vulnerability is in the shared parser/import code path that downstream products call into. When an affected application parses a MODEL file, data fields taken from the file are used without adequate bounds validation, so an attacker-controlled length or index causes writes past the end of an allocated buffer. Depending on heap layout and the attacker's control of the overwritten data, outcomes range from a crash (denial of service) to data corruption to code execution within the hosting process. Because the vulnerable code lives in a shared component, the patch surface spans every Autodesk product that links it, and the attack surface is limited to file parsing rather than network services - consistent with the AV:L/UI:R vector.
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
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
File must be opened locally by a user so AV:L and UI:R; no prior auth needed to parse the file (PR:N); memory-corruption RCE yields full C:H/I:H/A:H in the user's process (S:U).
Primary rating from Vendor (autodesk).
CVSS VectorVendor: autodesk
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
Autodesk Shared Components, a library embedded across the company's Autodesk design and engineering toolset, contains an out-of-bounds write flaw (CVE-2025-10900) that can be triggered when a user opens a maliciously crafted MODEL file, potentially allowing an attacker to execute code with that user's privileges. The risk is concentrated in engineering, design, and any team that routinely exchanges MODEL files with external partners or downloads them from untrusted sources, where a single opened file could expose local intellectual property, credentials, and the integrity of that workstation. No vendor-released patch and no public exploit were identified at time of analysis, so leadership should treat this as a manageable but unmitigated exposure that depends primarily on user behavior and file-handling controls.
No vendor-released patch identified at time of analysis. Interim mitigations: block or quarantine MODEL files from untrusted sources at email and web gateways, open external design files only in sandboxed or disposable virtual machines, enforce least privilege so affected users do not hold local administrative rights, apply application allowlisting and EDR monitoring for Autodesk processes, restrict who can receive external MODEL files, and monitor the vendor advisory for a fixed version to deploy.
Threat Intelligence Overview
NVD
CVE.org
EPSS
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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
More in Shared Components
View allHeap-based buffer overflow in Autodesk Shared Components - the shared file-parsing libraries used by multiple Autodesk a
Out-of-bounds write in Autodesk Shared Components allows local attackers to execute arbitrary code in the context of the
Memory corruption in the Autodesk Shared Components parser that handles CATPART files lets an attacker execute arbitrary
Out-of-bounds write in Autodesk shared components allows local attackers to execute arbitrary code, corrupt data, or cra
Out-of-bounds write in Autodesk products' CATPART file parser enables local attackers to achieve arbitrary code executio
A maliciously crafted PRT file, when parsed through certain Autodesk products, can force a Memory Corruption vulnerabili
A maliciously crafted PRT file, when parsed through certain Autodesk products, can force a Memory Corruption vulnerabili
An out-of-bounds read in Autodesk Shared Components can be triggered when a user opens or imports a maliciously crafted
An out-of-bounds read in Autodesk shared components lets an attacker crash an affected Autodesk application, read memory
Memory corruption in Autodesk Shared Components allows an attacker to execute arbitrary code in the context of the curre
Memory corruption in Autodesk Shared Components allows arbitrary code execution when a user opens a maliciously crafted
Parsing a maliciously crafted CATPRODUCT (CATIA assembly) file in Autodesk products that rely on the affected shared com
GitHub PoC
Exploit-DB