Autodesk Shared Components CVE-2025-10884
HIGHAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious CATPART file
-
DeliveryDeliver via email or shared CAD repository
-
ExploitVictim opens file in Autodesk product
-
ExecutionTrigger out-of-bounds write in parser
-
ImpactExecute arbitrary 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 user to open a maliciously crafted CATPART (CATIA V5 part) file in an affected Autodesk product that embeds the vulnerable shared-components parsing library; the out-of-bounds write is triggered during file parsing. Limiting factors: the vector is local (AV:L) with mandatory user interaction (UI:R) - there is no remote or unauthenticated network exploitation path, so the attacker must socially engineer the victim into opening an untrusted CATPART file. Code execution occurs only in the context of the current user process (S:U), bounding impact to that user's privileges. Risk is concentrated in workflows that routinely ingest externally-sourced CAD files (supplier exchanges, model-sharing portals); environments that do not open untrusted CATPART files are effectively unexposed. |
| Impact | This is a locally-exploitable, file-parsing memory-corruption flaw whose signals are internally consistent rather than conflicting. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 7.8 HIGH) correctly describes a client-side bug: there is no network vector - exploitation requires a victim to open an attacker-supplied CATPART file (AV:L + UI:R), so this is NOT a remotely-reachable server flaw despite the 'RCE' tag. No EPSS score was supplied, so quantitative exploitation probability cannot be stated. The vulnerability is NOT in CISA KEV and no public exploit code was provided in the intelligence, yielding 'no public exploit identified at time of analysis.' The combined picture is a genuine high-impact RCE primitive (OOB write, CWE-787, full C/I/A loss in the current process) gated behind meaningful user interaction and local delivery - a real priority for environments that routinely open externally-sourced CAD files, but materially lower urgency than a network-exploitable or actively-exploited bug. The main uncertainty is scope of affected products: the CPE lists only 'autodesk:shared_components' with a wildcard version and the advisory enumerates specific product versions not reproduced here - verify exact affected Autodesk products and fixed builds against advisory ADSK-SA-2025-0024. |
| Exploit ScenarioDerived | An attacker emails or shares a maliciously crafted CATPART file disguised as a legitimate CAD part, or plants it on a model-sharing/supplier portal. When an engineer opens it in an affected Autodesk product, the flawed parser performs an out-of-bounds write, allowing the attacker to crash the application, corrupt data, or execute arbitrary code in the context of the current user. No public proof-of-concept was identified; the local attack vector and required user interaction (AV:L/UI:R) mean exploitation depends on social engineering the victim into opening the file. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
Out-of-bounds write in Autodesk Shared Components (the shared CAD file-parsing library embedded across multiple Autodesk products) allows attackers to crash the application, corrupt data, or execute arbitrary code in the context of the current user process when a malicious CATPART (CATIA V5 part) file is opened. Per the assessed CVSS 3.1 vector AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, exploitation is local and requires user interaction: there is no remote or unauthenticated network path, and the attacker must socially engineer a victim into opening an untrusted CATPART file. No public exploit code has been identified at time of analysis, and the vulnerability is not listed as confirmed actively exploited (CISA KEV); risk is concentrated in environments that routinely ingest externally sourced CAD files such as supplier exchanges and model-sharing portals. Affected products are identified through the CPE cpe:2.3:a:autodesk:shared_components, with Autodesk's advisory adsk-sa-2025-0024 documenting the issue.
RemediationAI
Apply the fixed release specified in Autodesk security advisory ADSK-SA-2025-0024 (https://www.autodesk.com/trust/security-advisories/adsk-sa-2025-0024); the provided input does not include a specific patched version number, so the advisory must be consulted for the exact version per affected product, and no vendor-released patch version is independently confirmed from the available data. Where immediate updating is not possible, the most effective compensating control is to prevent the vulnerable parser from ever seeing untrusted input: block or strip CATPART attachments at email and web gateways, and deny download/import of externally sourced CATIA V5 part files into trusted CAD workflows - the trade-off is loss of supplier and partner model interchange, which may require a quarantined review workstation instead. Enforce allow-listing of trusted file sources and scan inbound CAD files with content-inspection tooling before they reach an Autodesk client; this reduces but does not eliminate exposure because malformed files can be obfuscated. Run Autodesk products that consume CATPART files under least-privilege, non-administrative accounts or in a sandboxed/VDI environment, which does not prevent the crash or in-process corruption but bounds the blast radius of any code execution to the current user process. Given the user-interaction requirement, reinforce awareness that opening unexpected or unsolicited CAD files from external parties is the primary delivery path.
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 is classified as CWE-787 (Out-of-Bounds Write), a memory-corruption weakness in which the parser writes data past the boundaries of an allocated buffer while handling a crafted CATPART file. The affected component is Autodesk Shared Components (CPE cpe:2.3:a:autodesk:shared_components), a library shared across Autodesk applications and therefore inherited by any product that embeds it - which explains the broad tag set (RCE, Buffer Overflow, Memory Corruption, Shared Components) despite a single CPE entry, and why a single malformed CATIA V5 part file can trigger the same flaw in multiple Autodesk desktop clients. The root cause is a lack of proper bounds validation on file-supplied length or index values during parsing of the CATPART structure; because the write occurs in-process, successful corruption can be steered toward control-flow hijack and code execution at the privilege level of the user who opened the file (scope unchanged, S:U). The CVSS vector AV:L/AC:L/PR:N/UI:R indicates no privileges are required but network delivery is not a viable vector and a human must open the file, so the realistic attack chain is a phishing- or supply-chain-style delivery of a weaponizable CAD file rather than a direct network exploit.
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 privileges needed (PR:N); reliable OOB write yields code execution in-process with full C/I/A loss, AC:L.
Primary rating from Vendor (autodesk).
CVSS VectorVendor: autodesk
DescriptionCVE.org
AA maliciously crafted CATPART 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, the shared CAD file-parsing library used across multiple Autodesk products, contains a high-severity out-of-bounds write that can be triggered when a user opens a malicious CATIA V5 part file. The practical business exposure is concentrated in engineering and design teams that routinely ingest CAD files from suppliers, partners, or public portals, where a successful exploit could corrupt design data, disrupt project timelines, or allow code execution under the victim's user privileges. Leadership should treat this as a workflow and third-party file-exchange risk, not just an isolated workstation issue, because the affected library is embedded across Autodesk products and no vendor-released patch has been identified at time of analysis.
No vendor-released patch identified at time of analysis. Interim mitigations: block or quarantine untrusted CATPART files at email and web gateways; prohibit opening externally sourced CAD files unless validated; enforce least privilege for CAD workstations; use application allowlisting and endpoint detection; isolate or sandbox file parsing where possible; monitor Autodesk advisory adsk-sa-2025-0024 and deploy the vendor patch when released.
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.
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
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB