Autodesk Shared Components CVE-2025-9457
HIGHAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted PRT file to victim
-
DeliveryVictim opens file in Autodesk product
-
ExploitTrigger heap overflow in shared parser
-
ExecutionExecute arbitrary code as current user
-
ImpactCompromise engineering workstation
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
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 a maliciously crafted PRT (part) file within an affected Autodesk product that uses the vulnerable Autodesk Shared Components parser; the triggering action is the file-parsing operation itself. Per the CVSS vector (AV:L, UI:R, PR:N), no authentication or prior privileges are needed, but local access to the target and active user interaction (opening the malicious file) are mandatory - there is no remote or network-triggered path. The principal limiting factors are the need for social-engineering delivery of the file and the reliance on the user choosing to open untrusted PRT content, and impact is bounded to the privileges of the current process/user. |
| Impact | This is a credible but not emergency-tier priority. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R) describes a local, user-interaction-dependent file-parsing flaw: an attacker cannot reach it remotely over a network and must convince a victim to open a malicious PRT file in an affected Autodesk product. High confidentiality, integrity, and availability impact (C:H/I:H/A:H) is justified because successful exploitation yields arbitrary code execution in the context of the current process, consistent with the CWE-122 heap-based buffer overflow. No EPSS score, CISA KEV listing, or public proof-of-concept was supplied in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation - the 7.8 'High' rating reflects impact potential, not demonstrated real-world weaponization. The dominant mitigating factor is the mandatory user interaction and local attack vector, which places this in the 'open-a-malicious-document' class typical of CAD/engineering file-format bugs rather than a wormable or internet-facing threat. Net: patch on a normal prioritized cycle, prioritizing users who routinely open third-party PRT files, but this is not a drop-everything issue absent any exploitation signal. |
| Exploit ScenarioDerived | An attacker crafts a malicious PRT part file and delivers it to a victim via email, a shared project repository, or a supplier file exchange. When the engineer opens the file in a vulnerable Autodesk product, the shared parsing component triggers a heap memory corruption, allowing the attacker to execute arbitrary code with that user's privileges. The local vector and required user interaction (AV:L/UI:R) mean this depends on social engineering; no public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
Memory corruption in Autodesk Shared Components allows an attacker to execute arbitrary code in the context of the current process when a user opens a maliciously crafted PRT part file. The flaw is a heap-based buffer overflow (CWE-122) rated CVSS 7.8 and, per the vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), requires no credentials or prior privileges but does require local access to the target and active user interaction - meaning social engineering to get the victim to open untrusted PRT content is a prerequisite, and any code execution is bounded by the privileges of that process. There is no public exploit identified at time of analysis, no POC published in the provided intelligence, and the CVE is not listed in CISA KEV; the practical risk is credible engineering-workstation compromise rather than an internet-facing emergency.
RemediationAI
Apply the fixed builds enumerated in Autodesk security advisory ADSK-SA-2025-0024 (https://www.autodesk.com/trust/security-advisories/adsk-sa-2025-0024) - patch status and exact fixed version numbers are not confirmed in the intelligence provided here, so treat the advisory as the source of truth and update every Autodesk product that consumes Autodesk Shared Components, using Autodesk Access (https://www.autodesk.com/products/autodesk-access/overview) to push the current release. Until patched builds are deployed, compensating controls should target the delivery-and-open step that exploitation depends on: strip or quarantine inbound .prt attachments and PRT downloads at the email and web gateway, and rely on Windows Attachment Manager / Mark-of-the-Web to add friction when users open part files from untrusted sources - the trade-off is real workflow disruption for engineering teams that legitimately exchange part files, so allow-list known partner sources rather than blocking the extension globally. Run Autodesk products under standard, non-administrative user accounts, because the CVSS vector's S:U scope means successful exploitation is contained to that process's privileges; this does not prevent the overflow or the resulting crash, it only limits blast radius. Where the product exposes trusted-location or file-loading restrictions, restrict loading of PRT content to vetted directories, and keep OS and application-level exploit mitigations (ASLR, DEP, CFG) enabled, since heap-corruption exploitation is materially harder with them active.
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 shared parsing library consumed by multiple Autodesk applications, which is why the single CPE in the intelligence feed is cpe:2.3:a:autodesk:shared_components:*:*:*:*:*:*:*:* with a wildcard version rather than a product-specific entry - the exposure follows whichever Autodesk product embeds the vulnerable parser and opens PRT (part) files. Root cause is CWE-122, heap-based buffer overflow: the parser trusts size or length fields inside the PRT file and performs a memory copy into a heap allocation that is smaller than the attacker-supplied data, corrupting adjacent heap metadata and objects. Because the overflow is on the heap and occurs during routine file parsing, an attacker who controls the file contents can shape the heap layout and redirect execution, yielding arbitrary code execution at the privilege level of the process that opened the file. The CVSS 3.1 vector underpins the scope of the issue: AV:L reflects that the malicious file must be opened locally rather than delivered over a network service, PR:N confirms no authentication is needed, UI:R confirms a user must open the crafted file, S:U confirms impact does not cross a security boundary beyond the affected process, and C:H/I:H/A:H confirms full confidentiality, integrity, and availability impact on that process.
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 credentials needed (PR:N); heap-corruption code execution yields full C:H/I:H/A:H within the unchanged process scope.
Primary rating from Vendor (autodesk).
CVSS VectorVendor: autodesk
DescriptionCVE.org
A maliciously crafted PRT 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 Shared Components contains a high-severity memory-corruption flaw that can let an attacker execute code on an engineering workstation when a user opens a malicious PRT file. The issue is not remotely exploitable and no public exploit identified at time of analysis, but because no vendor-released patch identified at time of analysis, affected design and engineering teams remain exposed to targeted social-engineering attempts. Leadership should prioritize protecting users who regularly open external or untrusted PRT content.
No vendor-released patch identified at time of analysis; restrict opening untrusted PRT files, block PRT attachments at email/web gateways where feasible, enforce least privilege, application allowlisting, EDR monitoring for Autodesk process anomalies, and user awareness training. Isolate engineering workstations from high-risk network segments until a vendor patch is available.
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.
A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.
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 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
Out-of-bounds read in Autodesk Shared Components allows local attackers to cause a crash, read sensitive memory, or pote
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB