Autodesk Shared Components CVE-2025-10899
HIGHAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted MODEL file to victim
-
DeliveryUser opens file in Autodesk product
-
ExploitTrigger out-of-bounds write in parser
-
ExecutionCorrupt process memory
-
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 an attacker-supplied, maliciously crafted MODEL file in an affected Autodesk product that links the vulnerable shared components (per CPE cpe:2.3:a:autodesk:shared_components). There is no network-triggerable path: the CVSS vector is AV:L with UI:R, so a victim's interactive action (opening/importing the file) is mandatory, and the code executes only in the context of the current user process - limiting factors are the need for file delivery plus user interaction, and the absence of privilege escalation or scope change (S:U). No specific non-default configuration is called out in the description beyond use of the affected parsing components. |
| Impact | 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) accurately frames this as a high-severity but NOT remotely-triggerable flaw: the attack vector is Local (AV:L) and requires user interaction (UI:R), meaning a victim must be convinced to open a maliciously crafted MODEL file in an affected Autodesk product. This is a classic client-side file-parsing memory-corruption bug (CWE-787 Out-of-Bounds Write), not a server-side or network-exposed vulnerability. Key exploitation signals are MISSING: no EPSS score was provided, the CVE is NOT listed in CISA KEV, and no public proof-of-concept is referenced - so there is no evidence of active exploitation or weaponization. The practical risk is therefore moderate and gated by social engineering (the attacker must deliver a file and the user must open it); it is a real patch-priority item for environments running Autodesk CAD software, but it is not a mass-exploitable internet-facing emergency. Note that while PR:N marks it unauthenticated, the AV:L + UI:R combination means exploitation depends entirely on tricking a local user, which substantially limits real-world weaponization compared to a network-vector RCE. |
| Exploit ScenarioDerived | An attacker crafts a malicious MODEL file and delivers it to a victim via email, a shared project repository, or a compromised file-exchange site. When the victim opens the file in a vulnerable Autodesk product that uses the affected shared components, the out-of-bounds write is triggered, potentially corrupting memory and allowing arbitrary code execution in the context of the current user. No public exploit code has been identified at time of analysis. |
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 allows a maliciously crafted MODEL file to corrupt memory when the file is parsed by an affected Autodesk product, giving an attacker the ability to crash the application, corrupt data, or execute arbitrary code in the context of the current user process. The flaw is rated CVSS 3.1 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), so it is not remotely triggerable: an attacker must deliver a crafted MODEL file and convince a user to open or import it, and exploitation is bounded by the user's own privileges with no scope change. No public exploit code has been identified at time of analysis and there is no indication of confirmed active exploitation (no CISA KEV listing); no EPSS score was supplied with the available intelligence.
RemediationAI
Apply the fixed release specified in Autodesk's security advisory ADSK-SA-2025-0024 (https://www.autodesk.com/trust/security-advisories/adsk-sa-2025-0024), which documents the patched shared components build for each affected product; an exact patched version number is not confirmed in the available data, so verify the version listed in the advisory rather than relying on a generic update prompt. Until systems are updated, the practical compensating controls target the delivery vector rather than the parser: block or quarantine inbound MODEL file attachments at the email/web gateway, and enforce Microsoft Defender SmartScreen/Mark-of-the-Web and macro-independent attachment policies so untrusted files cannot be opened silently - the trade-off is potential friction for legitimate engineering file exchange. Restrict interactive use of affected Autodesk applications to accounts with least privilege to limit the impact of any code that does execute, noting this contains rather than prevents exploitation. Application allowlisting and EDR rules that flag an Autodesk process spawning unexpected child processes (e.g., cmd.exe, PowerShell, script interpreters) provide detection for exploitation attempts, at the cost of tuning effort and possible false positives on legitimate automation. Opening MODEL files exclusively from trusted sources and verifying file provenance before import remains the primary human-side 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 vulnerability is an out-of-bounds write (CWE-787) in the file-parsing code of Autodesk Shared Components, a library shared across multiple Autodesk desktop products. CWE-787 covers writes past the end (or before the start) of an allocated buffer, typically caused by missing or incorrect bounds/length validation when attacker-controlled size fields or counts in the parsed file drive memory operations such as indexed writes or memory copies. Here the untrusted input is a MODEL file: its internal structure and length fields are consumed by the shared parsing component, and a crafted file can cause the parser to write beyond its intended buffer. Memory corruption of this class produces the disclosed outcomes - denial of service (crash), integrity loss (data corruption), and, under the attacker's control of layout, arbitrary code execution strictly within the current process context. The CPE cpe:2.3:a:autodesk:shared_components:*:*:*:*:*:*:*:* uses a wildcard version, indicating the advisory does not pin a single release and that any product build linking an unpatched copy of the shared components is in scope. The assessed vector (AV:L, UI:R, S:U, PR:N) confirms the parser is not reachable over the network and that no privileges are required beyond those the victim already holds.
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-parsing bug needs no privileges (PR:N) but requires the victim to open a malicious file locally, so AV:L and UI:R; memory corruption yields full C/I/A impact in-process.
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 contains a high-severity memory-corruption flaw (CVE-2025-10899) that can be triggered when a user opens a maliciously crafted MODEL file in affected Autodesk products. Because exploitation requires local file interaction and no patch is currently available, design, engineering, and manufacturing teams remain exposed to application crashes, data corruption, or code execution under the user's own privileges. Leadership should prioritize user awareness, file-source controls, and vendor-patch tracking to protect critical design workflows and intellectual property.
No vendor-released patch identified at time of analysis. Interim mitigations: block or quarantine untrusted MODEL files at email/web gateways; enforce user awareness to avoid opening unsolicited design files; run Autodesk applications with least privilege; use application allowlisting, endpoint detection, and sandboxing for file parsing; restrict import paths to trusted repositories; and monitor for crash/corruption indicators.
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