CVE-2026-72895: Siemens SIMATIC IPC Secure Boot Bypass via Embedded Test Key — Detection and Remediation Guide

CISA has published ICS advisory ICSA-26-295-07 covering CVE-2026-72895 (CVSS v3 7.7, High) in multiple Siemens SIMATIC industrial PC lines. The vulnerability class is Use of Default Cryptographic Key: the UEFI firmware on affected devices trusts a test signing key that was never meant to exist in production hardware. Any operating system bootloader or UEFI application signed with that test key will be accepted by the platform even when Secure Boot is enabled — which means the control defenders rely on as the anchor of the pre-boot trust chain is effectively a paper wall on these devices.

Siemens has released fixed BIOS/firmware versions and recommends updating immediately. If you operate SIMATIC IPCs anywhere in your environment — engineering workstations, HMI hosts, line-side controllers, thin clients in process areas — treat this as a priority patching event. The affected products sit in Critical Infrastructure sectors by design.

Why This Matters More Than the CVSS Suggests

A 7.7 on a local-access firmware flaw can look deceptively manageable. In practice, Secure Boot bypass is one of the highest-leverage primitives an attacker can hold:

• Bootkit and boot-loader implant territory. An adversary who can boot an attacker-signed UEFI application or OS image can persist below the operating system — surviving OS reinstallation, disk re-imaging of the OS volume, and most EDR visibility. This is the same trust-chain failure pattern we've seen weaponized in prior Secure Boot key-compromise incidents (the PKfail research and the BlackLotus bootkit campaign taught the industry how expensive this gets).
• OT realities amplify dwell time. SIMATIC IPCs are frequently deployed for 10–15 year lifecycles, are rarely rebooted, and often sit on segments with minimal EDR coverage. A firmware-level implant on an HMI host can go unobserved for years.
• The 'Secure Boot is on' checkbox becomes a false assurance. Your compliance evidence (CIS Control 6, NIST CSF PR.PT, IEC 62443 boot-integrity expectations) may claim boot integrity that the platform cannot actually deliver until patched.

Technical Analysis

CVE: CVE-2026-72895 — Use of Default Cryptographic Key (CWE-321 family) CVSS v3: 7.7 (High) Vendor advisory: CISA ICSA-26-295-07 — https://www.cisa.gov/news-events/ics-advisories/icsa-26-295-07

Affected products and fixed versions

How the vulnerability works (defender's view)

UEFI Secure Boot validates boot components against the platform's allowed-signature database (db) and forbidden-signature database (dbx). On the affected IPCs, a test signing key — used internally during manufacturing/development — was left trusted in the production firmware's signature chain. The consequences:

1. An attacker with physical access, or who has achieved code execution sufficient to modify the EFI System Partition / boot order (e.g., a compromised admin context on the IPC's host OS), places a bootloader or UEFI application signed with the known test key on the device.
2. At next boot, the firmware verifies the binary against the trusted test key and loads it, despite Secure Boot being reported as 'Enabled.'
3. The attacker's pre-OS code executes before any OS-level security control (EDR, application allowlisting, BitLocker integrity checks dependent on measured boot) can observe or block it.

Exploitation requirements: Local access — either physical (USB boot media) or privileged OS-level code execution to stage boot components and modify BootOrder/ESP contents. There is no remote vector by itself, but it chains naturally with any remote-to-local foothold and dramatically raises the impact of one.

Exploitation status: As of this advisory, neither CISA nor Siemens reports confirmed in-the-wild exploitation, and CVE-2026-72895 is not listed in the CISA KEV at time of writing. Treat it as a high-value theoretical-to-practical gap: test keys are static, and once they circulate, every unpatched unit is exposed. Do not wait for a KEV entry to patch OT firmware trust-chain flaws.

Detection & Response

Detection here splits into two problems: (1) identifying vulnerable devices (inventory and Secure Boot state validation) and (2) detecting staging behavior — the host-OS activity an attacker needs to abuse the flaw (ESP modification, boot-order manipulation, UEFI variable writes). Firmware-level compromise itself is largely invisible to endpoint tooling, which is exactly why pre-execution staging telemetry matters.

---
title: UEFI Boot Configuration or Secure Boot Modification Attempt
description: Detects command-line manipulation of boot configuration, Secure Boot UEFI variables, or mounting of the EFI System Partition — the staging behavior required to abuse CVE-2026-72895 on Siemens SIMATIC IPCs.
id: 3f7a2c91-6b84-4d1e-9c53-8a2f7d5e1b04
status: experimental
references:
  - https://www.cisa.gov/news-events/ics-advisories/icsa-26-295-07
  - https://attack.mitre.org/techniques/T1542/001/
author: Security Arsenal
date: 2026/10/21
tags:
  - attack.persistence
  - attack.defense_evasion
  - attack.t1542.001
logsource:
  category: process_creation
  product: windows
detection:
  selection_bcdedit:
    Image|endswith: '\bcdedit.exe'
    CommandLine|contains:
      - '{bootmgr}'
      - '/set'
      - 'bootsequence'
  selection_mountvol_esp:
    Image|endswith: '\mountvol.exe'
    CommandLine|contains: '/s'
  selection_powershell_uefi:
    Image|endswith:
      - '\powershell.exe'
      - '\pwsh.exe'
    CommandLine|contains:
      - 'Set-SecureBootUEFI'
      - 'Get-UEFISecureBootCertificates'
      - 'BootOrder'
  condition: 1 of selection_*
falsepositives:
  - Authorized firmware update and imaging workflows on Siemens IPCs
  - IT administration during OS deployment
level: high
---
title: Boot Loader Binary Written to EFI System Partition
description: Detects file writes of PE executables into the EFI System Partition path, consistent with staging an attacker-signed bootloader to exploit a Secure Boot trust failure such as CVE-2026-72895.
id: 8c1d4e62-3a97-4f0b-b2d6-5e9c1a7f3d08
status: experimental
references:
  - https://www.cisa.gov/news-events/ics-advisories/icsa-26-295-07
  - https://attack.mitre.org/techniques/T1542/001/
author: Security Arsenal
date: 2026/10/21
tags:
  - attack.persistence
  - attack.t1542.001
logsource:
  category: file_event
  product: windows
detection:
  selection:
    TargetFilename|contains:
      - '\EFI\Boot\'
      - '\EFI\Microsoft\Boot\'
    TargetFilename|endswith: '.efi'
  filter_known_updaters:
    Image|endswith:
      - '\TiWorker.exe'
      - '\svchost.exe'
      - '\poqexec.exe'
  condition: selection and not filter_known_updaters
falsepositives:
  - Vendor firmware update utilities
  - Dual-boot provisioning tools
level: high
---
title: Linux ESP Mount and EFI Binary Staging on Industrial Hosts
description: Detects mounting of the EFI System Partition and placement of .efi binaries on Linux-based industrial PCs, a prerequisite for abusing a trusted test signing key under CVE-2026-72895.
id: b24e9f05-71c3-4a8d-9e1b-6f4d2c8a5e17
status: experimental
references:
  - https://www.cisa.gov/news-events/ics-advisories/icsa-26-295-07
  - https://attack.mitre.org/techniques/T1542/001/
author: Security Arsenal
date: 2026/10/21
tags:
  - attack.persistence
  - attack.t1542.001
logsource:
  category: process_creation
  product: linux
detection:
  selection_mount:
    Image|endswith:
      - '/mount'
      - '/efibootmgr'
    CommandLine|contains:
      - '/boot/efi'
      - 'efivarfs'
      - 'efi'
  selection_write:
    Image|endswith:
      - '/cp'
      - '/dd'
      - '/rsync'
    CommandLine|contains:
      - '.efi'
      - '/boot/efi/'
  condition: 1 of selection_*
falsepositives:
  - Legitimate kernel and bootloader updates (apt/dnf transactions)
  - Firmware maintenance windows
level: high

// Hunt: Boot configuration tampering on industrial hosts (potential CVE-2026-72895 staging)
// Scope to your SIMATIC IPC / engineering workstation device groups in Defender or Sentinel.
let Lookback = 14d;
DeviceProcessEvents
| where TimeGenerated > ago(Lookback)
| where FileName in~ ("bcdedit.exe", "mountvol.exe", "efibootmgr", "fwupdmgr", "fwupd")
   or (FileName in~ ("powershell.exe", "pwsh.exe")
       and ProcessCommandLine has_any ("Set-SecureBootUEFI", "BootOrder", "UEFISecureBootCertificates"))
| project TimeGenerated, DeviceName, FileName, ProcessCommandLine, InitiatingProcessAccountName, InitiatingProcessFileName, ReportId
| sort by TimeGenerated desc;

-- Artifact: Hunt.SecureBoot.Staging
-- Identify staging activity relevant to Secure Boot trust abuse (CVE-2026-72895):
-- boot config tooling execution plus files in the EFI System Partition.
SELECT Pid, Name, CommandLine, Exe, Username, CreateTime
FROM pslist()
WHERE CommandLine =~ '(bcdedit|efibootmgr|Set-SecureBootUEFI|mountvol.*/s|BootOrder)'

// Companion file sweep (run on hosts with the ESP mounted at S: or /boot/efi):
// SELECT FullPath, Size, Mtime FROM glob(globs='S:/EFI/**/*.efi')
// WHERE NOT FullPath =~ '(?i)microsoft|siemens'

The following PowerShell script inventories a Windows-based SIMATIC IPC for Secure Boot state, firmware version, and boot configuration drift. Run it across your OT Windows fleet (via your EDR live-response or a signed management channel — not an unauthenticated share).

# Requires: Run elevated on the target IPC.
# Purpose: Verify Secure Boot state, capture firmware version, and baseline boot config
#          on Siemens SIMATIC IPC hosts (CVE-2026-72895 exposure assessment).

$report = [ordered]@{}
$report.Hostname = $env:COMPUTERNAME

# 1) Secure Boot state — 'True' is NOT sufficient alone on affected firmware,
#    but 'False' or unsupported is an immediate finding.
try {
    $report.SecureBootEnabled = Confirm-SecureBootUEFI
} catch {
    $report.SecureBootEnabled = "UNSUPPORTED-OR-LEGACY-BIOS: $($_.Exception.Message)"
}

# 2) Firmware identification — compare against fixed versions:
#    BX-21A >= 31.01.13 | RW-543A >= 1.1.4 | IPC227G/277G/277G PRO/327G/377G >= 28.01.15
$bios = Get-CimInstance Win32_BIOS
$report.Manufacturer    = $bios.Manufacturer
$report.BIOSVersion     = $bios.SMBIOSBIOSVersion
$report.SerialNumber    = $bios.SerialNumber

$cs = Get-CimInstance Win32_ComputerSystem
$report.Model = $cs.Model

# 3) Flag known-affected model families for patch prioritization
$affectedModels = 'BX-21A','RW-543A','IPC227G','IPC277G','IPC327G','IPC377G'
$report.PotentiallyAffected = ($affectedModels | Where-Object { $report.Model -like "*$_*" }) -ne $null

# 4) Boot configuration snapshot for drift detection
$report.BootMgrPath = (bcdedit /enum '{bootmgr}' | Out-String)

# 5) dbx revocation freshness — stale dbx is a compounding risk on UEFI trust-chain issues
try {
    $dbx = Get-SecureBootUEFI -Name dbx -ErrorAction Stop
    $report.DbxPresent = $true
    $report.DbxBytes   = $dbx.Bytes.Length
} catch {
    $report.DbxPresent = "ERROR: $($_.Exception.Message)"
}

$report | ConvertTo-Json -Depth 4

Remediation

1. Patch firmware — this is the only complete fix. Update each affected product to the fixed BIOS/firmware version or later:

• SIMATIC IPC BX-21A → 31.01.13+
• SIMATIC IPC RW-543A → 1.1.4+
• SIMATIC IPC 227G / 277G / 277G PRO / 327G / 377G → 28.01.15+

Obtain updates only via Siemens' official support channels referenced in ICSA-26-295-07 and Siemens' ProductCERT advisory. Verify firmware integrity hashes where published.

2. Follow the advisory chain:

• CISA ICS Advisory: https://www.cisa.gov/news-events/ics-advisories/icsa-26-295-07
• Register for Siemens ProductCERT notifications to catch the follow-on CSAF documents.

3. Until patched, apply compensating controls (CISA's standard ICS guidance applies directly):

• Physical access control on all affected IPCs — USB boot is the lowest-effort vector for this flaw. Lock panels, disable or port-control front USB where operationally feasible, and log physical access events.
• Disable boot from removable media in BIOS setup and set a supervisor/administrator BIOS password on every affected unit. This does not fix the trusted key, but it raises the bar against casual USB boot attacks.
• Minimize exposure per CISA ICS best practice: keep IPCs behind firewalls, isolated from business networks, with no direct internet reachability; require VPN plus MFA for any remote access path.
• Protect the ESP and UEFI variables from the host OS: restrict local admin rights on the IPC's Windows/Linux installation, enforce application allowlisting, and alert on the staging behaviors covered in the detection section.

4. Post-patch verification: after firmware update, re-run the inventory script above, confirm BIOS version meets the fixed baseline, confirm Secure Boot reports enabled, and re-baseline boot configuration so future drift is detectable.

5. Plan for OT change windows now. Firmware updates on IPCs require downtime coordination with operations. Given there is no remote exploitation vector today, a scheduled-but-prompt maintenance cycle is defensible — but do not let these units slide to the 'someday' list. Test keys don't expire, and the longer they remain trusted in production, the more certain their eventual abuse becomes.

Bottom Line

CVE-2026-72895 is a trust-chain failure, not a memory-corruption bug — and trust-chain failures in OT hardware are exactly the kind of quiet, durable weakness sophisticated actors bank for later. Inventory your SIMATIC IPC fleet this week, stage the firmware updates into your next maintenance windows, and deploy the staging-behavior detections as a tripwire in the interim.

Related Resources

Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub