Solid Edge CVE-2025-40810

Exploitation requires a victim to open an attacker-crafted PRT (Solid Edge part) file in a vulnerable Solid Edge SE2024 (< V224.0 Update 14) or SE2025 (< V225.0 Update 6) installation; there is no network-triggerable path. Key limiting factors: the CVSS vector is local (AV:L) with required passive user interaction (UI:P) and high attack complexity (AC:H), meaning an attacker must both socially engineer file delivery and reliably control memory layout during PRT parsing. No authentication is needed by the attacker (PR:N), but code execution is confined to the opening user's process context, so impact scales with that user's privileges rather than granting automatic system-level access.

This is a moderate-priority, not a drop-everything, issue. The Siemens-assigned CVSS 4.0 vector (AV:L/AC:H/AT:N/PR:N/UI:P, score 7.3) describes a client-side file-parsing out-of-bounds write (CWE-787): exploitation is local, requires high attack complexity, and depends on passive user interaction (a victim opening a malicious PRT file). All three exploitation-probability signals point the same direction and reinforce a lower urgency: EPSS is only 0.14% (3rd percentile), the CVE is NOT in CISA KEV, and no public exploit code is referenced - so there is no public exploit identified at time of analysis and no evidence of active exploitation. The high confidentiality/integrity/availability impact (VC/VI/VA:H) is real because code execution in the current user's process context is possible, but it is gated behind social engineering and a non-trivial exploit (AC:H), which is why the score lands at 7.3 rather than critical. No signals conflict here; the high impact is tempered consistently by the local vector, high complexity, and required user interaction. Treat as a standard patch-cycle item for engineering/CAD workstations rather than an emergency.

An attacker crafts a malicious Solid Edge PRT part file and delivers it to a targeted engineer via email, a shared project repository, or a supplier data exchange. When the victim opens the file in a vulnerable Solid Edge SE2024/SE2025 version, the malformed data triggers an out-of-bounds write during parsing, crashing the application or executing attacker-supplied code in the context of the current user. No public exploit code is identified at time of analysis, so weaponization would require independent development.