Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-9456: CWE-120 Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') in Autodesk Shared Components

0
High
VulnerabilityCVE-2025-9456cvecve-2025-9456cwe-120
Published: Mon Dec 15 2025 (12/15/2025, 23:36:32 UTC)
Source: CVE Database V5
Vendor/Project: Autodesk
Product: Shared Components

Description

A maliciously crafted SLDPRT 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.

AI-Powered Analysis

AILast updated: 12/16/2025, 00:02:40 UTC

Technical Analysis

CVE-2025-9456 is a classic buffer overflow vulnerability (CWE-120) identified in Autodesk Shared Components version 2026.0. The flaw occurs due to a lack of proper bounds checking when processing SLDPRT files, which are proprietary CAD part files used by Autodesk products. When a specially crafted SLDPRT file is parsed, the vulnerability triggers memory corruption, potentially allowing an attacker to execute arbitrary code within the context of the current process. The vulnerability is rated with a CVSS 3.1 base score of 7.8, indicating high severity. The attack vector is local (AV:L), requiring user interaction (UI:R) but no privileges (PR:N), and the scope remains unchanged (S:U). The impact on confidentiality, integrity, and availability is high, meaning an attacker could fully compromise the affected application and potentially the host system. No public exploits are known at this time, but the vulnerability's nature and severity make it a significant risk, especially for environments where untrusted SLDPRT files might be opened. Autodesk Shared Components are widely used across various Autodesk CAD products, making this a broad-reaching issue for users of the 2026.0 release. The vulnerability was reserved in August 2025 and published in December 2025, with no patches currently available, emphasizing the need for vigilance and interim mitigations.

Potential Impact

For European organizations, particularly those in manufacturing, engineering, and design sectors relying on Autodesk CAD tools, this vulnerability poses a substantial risk. Successful exploitation could lead to arbitrary code execution, allowing attackers to compromise sensitive design data, intellectual property, and potentially pivot within corporate networks. The high impact on confidentiality, integrity, and availability means that critical design workflows could be disrupted, leading to operational downtime and financial loss. Additionally, compromised systems could serve as footholds for further attacks, including espionage or ransomware. Given the local attack vector and requirement for user interaction, the threat is more pronounced in environments where users frequently exchange or open SLDPRT files from external or untrusted sources. The lack of known exploits currently provides a window for proactive defense, but the high severity score underscores the urgency of addressing this vulnerability.

Mitigation Recommendations

1. Monitor Autodesk's official channels closely for the release of security patches addressing CVE-2025-9456 and apply them immediately upon availability. 2. Implement strict file handling policies to restrict the opening of SLDPRT files from untrusted or unknown sources. 3. Employ application whitelisting and sandboxing techniques to limit the execution context of Autodesk applications, reducing the impact of potential exploitation. 4. Use endpoint detection and response (EDR) solutions to monitor for anomalous behavior indicative of exploitation attempts, such as unexpected memory access patterns or process injections. 5. Conduct user awareness training focused on the risks of opening unverified CAD files and encourage verification of file provenance. 6. Where feasible, isolate Autodesk software environments from critical network segments to contain potential breaches. 7. Regularly back up critical design data and verify backup integrity to ensure recovery capability in case of compromise. 8. Consider deploying runtime exploit mitigation technologies such as Data Execution Prevention (DEP) and Address Space Layout Randomization (ASLR) if not already enabled.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
autodesk
Date Reserved
2025-08-25T14:12:51.594Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69409d9cd9bcdf3f3d09c715

Added to database: 12/15/2025, 11:45:32 PM

Last enriched: 12/16/2025, 12:02:40 AM

Last updated: 12/16/2025, 9:14:33 PM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats