Autodesk Shared Components CVE-2025-10886
HIGHAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious MODEL file
-
DeliveryDeliver via email or shared repository
-
ExploitVictim opens file in Autodesk product
-
ExecutionTrigger buffer overflow in shared parser
-
ImpactExecute arbitrary code as current user
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Buffer copy size validation
MITRE ATT&CK
1 technique across 1 tactic: Execution 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 or parse an attacker-supplied, maliciously crafted MODEL file within an affected Autodesk product that uses the vulnerable shared components - this user interaction (UI:R) and the local attack vector (AV:L) are the primary limiting factors, as there is no network-facing exploitation path. No authentication or elevated privileges are needed by the attacker (PR:N), but code executes only with the privileges of the user who opens the file (scope unchanged), so impact is bounded by that user's context rather than system-wide. Risk is concentrated on workstations that routinely ingest externally sourced model/design files; environments that only open trusted, internally generated files face substantially lower realistic exposure. |
| Impact | This is a moderate-priority, not emergency, vulnerability. The CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) is driven by high impact (full code execution in the current process context) but is firmly gated by a LOCAL attack vector and REQUIRED user interaction - the attacker cannot reach the parser remotely and must convince a victim to open a malicious MODEL file. No EPSS score was provided, the CVE is NOT in the CISA KEV catalog, and no public proof-of-concept was supplied in the intelligence, so exploitation status is: no public exploit identified at time of analysis. There is no SSVC decision data in the input. The signals are internally consistent (no conflict between the local/UI-gated vector and the file-parsing description), so there is no network-vs-local discrepancy to flag; the main caveat is simply that real-world risk depends on social-engineering a user into opening attacker-supplied design files, which places this in the classic client-side file-format-parser bug category rather than the auto-exploitable, worm-capable tier. Treat it as a standard patch-cycle item, prioritized higher for workstations that routinely open untrusted CAD/MODEL files. |
| Exploit ScenarioDerived | An attacker emails or shares a maliciously crafted MODEL file (or stages it on a download/collaboration portal) and social-engineers an engineer into opening it in an affected Autodesk product. When the shared-component parser processes the malformed file, a buffer-overflow memory corruption is triggered, allowing arbitrary code execution in the context of the logged-in user. No public exploit code was identified at the time of analysis, so weaponization would require attacker development effort. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
Memory corruption in Autodesk's shared components (CWE-120, classic buffer overflow) can be triggered when an affected Autodesk application parses a maliciously crafted MODEL file, letting an attacker execute arbitrary code in the context of the user who opens the file. The issue carries a CVSS 3.1 score of 7.8 with a local attack vector, no privileges required (PR:N), and mandatory user interaction (UI:R), so exploitation hinges on convincing a target to open a hostile file rather than on any network-reachable service. No public exploit code and no CISA KEV listing were identified at time of analysis, and the independent assessment rates this as a moderate-priority rather than emergency issue, with realistic risk concentrated on design workstations that routinely ingest externally sourced model files.
RemediationAI
Apply the fixed shared-components update specified in Autodesk security advisory adsk-sa-2025-0024 (https://www.autodesk.com/trust/security-advisories/adsk-sa-2025-0024); no exact patched version number is provided in the available intelligence, so the advisory should be treated as the authoritative source for the current fixed build and for the affected product/version matrix. Where patching cannot be completed immediately, the most effective compensating control is to prevent untrusted MODEL files from reaching the parser: block or quarantine .model attachments at email and web gateways, disable or restrict file-association handlers so MODEL files are not parsed on double-click, and enforce an allowlist so only vetted internal sources supply design files - the trade-off is reduced workflow flexibility for external collaborators and a risk of false positives on legitimate CAD exchange. Run Autodesk applications under standard least-privilege user accounts rather than as local administrators or elevated service accounts, which does not prevent the memory corruption but bounds the impact of successful code execution to that user's context (consistent with the assessed scope-unchanged vector); the trade-off is occasional permission friction saving to protected directories. Application-level sandboxing, containerization, or Windows Defender Application Guard-style isolation for design tools reduces blast radius at the cost of performance overhead and possible plug-in incompatibility, and endpoint detection tuned to look for Autodesk processes spawning unusual child processes can catch post-exploitation behavior. Given that exploitation requires user interaction and there is no confirmed active exploitation, these measures should be sequenced as normal patch-cycle work rather than emergency response.
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 vulnerability resides in Autodesk shared components - a common code layer consumed by multiple Autodesk products, as reflected in the CPE string cpe:2.3:a:autodesk:shared_components:*:*:*:*:*:*:*:* with an unbounded version range. The root cause is CWE-120, Buffer Copy without Checking Size of Input (a classic buffer overflow): when the parser ingests a specially crafted MODEL file, an unchecked copy operation overruns a fixed-length memory buffer, corrupting adjacent memory and, with sufficient attacker control over the overwrite contents, enabling arbitrary code execution. The CVSS vector (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) shows a low-complexity local attack that requires no authentication or elevated privileges but does require user interaction (opening/parsing the file), with high confidentiality, integrity, and availability impact limited to the scope of the vulnerable component. Because the shared components are reused across products, the same malformed-file primitive is theoretically reachable from any Autodesk application that links the affected library and parses MODEL format input.
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 (AV:L, UI:R); no attacker privileges needed (PR:N); crafted-file parsing reliably triggers the overflow (AC:L) yielding full code execution (C/I/A:H).
Primary rating from Vendor (autodesk).
CVSS VectorVendor: autodesk
DescriptionCVE.org
A maliciously crafted MODEL file, when parsed through certain Autodesk products, can force a Memory corruption vulnerability. A malicious actor can leverage this vulnerability to execute arbitrary code in the context of the current process.
Executive ViewAI
Autodesk applications that utilize shared components are affected by a high-severity memory corruption vulnerability (CVE-2025-10886) that can be exploited when a user opens a malicious MODEL file, leading to arbitrary code execution on the workstation. While no public exploit identified at time of analysis and no CISA KEV listing, the absence of a vendor-released patch means that design workstations remain at risk, potentially exposing sensitive design data and enabling lateral movement within the network. Leadership should prioritize mitigation efforts because these workstations often handle valuable intellectual property and are used by engineers and designers who may routinely open externally sourced files.
Enforce application allowlisting, restrict opening of untrusted MODEL files, implement email and web filtering, deploy endpoint detection and response, conduct user awareness training, apply network segmentation, and follow principle of least privilege. No vendor-released patch identified at time of analysis.
Threat Intelligence Overview
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.
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 allOpening a maliciously crafted X_T (Siemens Parasolid) model file in an Autodesk product that bundles the affected Shared
Heap-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
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB