Siemens SIMATIC IPC CVE-2026-72895

Exploitation requires the attacker to already possess physical access or administrative access to the affected SIMATIC IPC, and to control the boot process (UI:A - the attacker must boot or install an OS/UEFI application signed with the embedded BIOS vendor test key). The specific precondition is the presence of the leftover vendor test key in the UEFI Secure Boot key database on firmware below the fixed versions (IPC BX-21A < V31.01.13, IPC RW-543A < V1.1.4, IPC227G/277G/277G PRO/327G/377G < V28.01.15). Limiting factors: the vector is local only (no remote exploitation), it depends on Secure Boot actually being enabled and relied upon as a trust boundary, and it requires either hands-on device access or existing administrative privilege - so a hardened physical/OT environment with restricted operator access substantially reduces real-world exposure.

This is a genuine but access-gated risk rather than a mass-exploitation threat. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:A) scores 8.4 (High) driven by full High impact to confidentiality, integrity and availability (VC:H/VI:H/VA:H) with no subsequent-system impact. The attack vector is Local, not Network, so remote mass-exploitation is not possible - the CVSS vector's PR:N conflicts with the description, which explicitly states the attacker needs 'physical or administrative access to the device'; this discrepancy should be verified, as the practical barrier to entry is materially higher than PR:N alone implies. No EPSS score, CISA KEV listing, or public POC was supplied in the intelligence, so there are no exploitation-probability or active-exploitation signals to corroborate the severity. No SSVC decision data was provided. The root cause (CWE-1394, leftover BIOS vendor test key in the UEFI Secure Boot DB) is a credible and recurring supply-chain class of flaw, but exploitation requires an attacker already positioned at or inside the device. Net assessment: patch-worthy for OT/ICS asset owners who rely on Secure Boot as a trust anchor, but the local-only vector and access prerequisites make this a targeted/insider-and-physical-access concern, not a widespread remote emergency.

An attacker with physical access (e.g., in a plant or substation) or administrative access to an affected SIMATIC IPC signs a malicious bootloader or UEFI application with the known BIOS vendor test key, then reboots the device to load it; because the test key is trusted in the Secure Boot key database, the malicious image boots even with Secure Boot enabled. No public exploit identified at time of analysis, though the trust-anchor nature means a crafted signed image fully defeats the boot integrity guarantee.