Autodesk Shared Components CVE-2025-9455

Exploitation requires a victim to open a maliciously crafted CATPRODUCT (CATIA assembly) file in an affected Autodesk product that relies on the vulnerable Autodesk shared components (per CPE cpe:2.3:a:autodesk:shared_components). Limiting factors: the attack vector is LOCAL (AV:L) with REQUIRED user interaction (UI:R) - the attacker cannot trigger this remotely or without the user actively opening the file, and no elevated privileges are needed (PR:N) but the resulting code runs only in the current user's context (S:U). There is no network-facing exposure and no automated/unattended exploitation path.

This is a high-severity but not high-urgency issue. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R) is explicitly LOCAL with required user interaction, meaning exploitation depends on a victim opening a maliciously crafted CATPRODUCT file - this is a client-side file-parsing flaw, not a remotely reachable network service. The 7.8 base score is driven by the high C/I/A impact (potential arbitrary code execution), not by ease of reach. No EPSS score, CISA KEV listing, or public POC was provided in the input, so there is no signal of active exploitation or weaponization; exploitation status is 'no public exploit identified at time of analysis.' The SSVC/automatable dimension is effectively low because each exploitation requires social-engineering a user into opening a file, making this targeted rather than wormable. Net assessment: patch in normal cycles prioritizing workstations that routinely open third-party CAD files, but this does not warrant emergency out-of-band response absent new exploitation signals. Note: vendor (Autodesk PSIRT) is the sole source and no affected version list or fixed version was supplied, so remediation scope must be confirmed against the Autodesk advisory.

An attacker emails or shares a malicious CATPRODUCT (CATIA assembly) file to an engineer, who opens it in a vulnerable Autodesk product that uses the affected shared components. The out-of-bounds read is triggered during parsing, allowing the attacker to crash the application, leak adjacent process memory, or achieve code execution in the context of the current user. No public proof-of-concept was identified in the provided data, and exploitation requires the user to actively open the crafted file (UI:R).