CVE-2026-72895: High severity Siemens SIMATIC IPC BX-21A vulnerability

Published Oct 13, 2026
·
Updated

A vulnerability has been identified in SIMATIC IPC BX-21A (All versions < V31.01.13), SIMATIC IPC RW-543A (All versions < V1.1.4), SIMATIC IPC227G / IPC277G / IPC277G PRO / IPC327G / IPC377G (All versions < V28.01.15). A BIOS vendor test key is present in the UEFI Secure Boot key database. This could allow a local attacker with physical or administrative access to the device to boot an operating system or UEFI application signed with that test key, bypassing UEFI Secure Boot protections even when Secure Boot is enabled, potentially leading to a full loss of confidentiality, integrity, and availability of the device.

Affected Software

7 affected components
Siemens SIMATIC IPC BX-21A<V31.01.13
Siemens SIMATIC IPC RW-543A<V1.1.4
Siemens Simatic Ipc227g<V28.01.15
Siemens Simatic Ipc277g<V28.01.15
Siemens SIMATIC IPC277G PRO<V28.01.15
Siemens Simatic Ipc327g<V28.01.15
Siemens Simatic Ipc377g<V28.01.15

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade SIMATIC IPC BX-21A to a version that resolves this vulnerability.

    Fixed in V31.01.13
  2. Upgrade

    Upgrade SIMATIC IPC RW-543A to a version that resolves this vulnerability.

    Fixed in V1.1.4
  3. Upgrade

    Upgrade SIMATIC IPC227G / IPC277G / IPC277G PRO / IPC327G / IPC377G to a version that resolves this vulnerability.

    Fixed in V28.01.15

Event History

Oct 13, 2026
CVE Published
via MITRE·09:18 AM
Data Sourced
via MITRE·09:18 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:17 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which systems need remediation?

Affected systems are SIMATIC IPC BX-21A versions earlier than V31.01.13, SIMATIC IPC RW-543A versions earlier than V1.1.4, and SIMATIC IPC227G, IPC277G, IPC277G PRO, IPC327G, and IPC377G versions earlier than V28.01.15.

2

What level of access does an attacker need?

Exploitation requires local physical or administrative access to the device. The attacker must be able to boot an operating system or UEFI application signed with the BIOS vendor test key.

3

Does enabling UEFI Secure Boot prevent exploitation?

No. The test key is present in the UEFI Secure Boot key database, allowing signed code using that key to bypass Secure Boot protections even when Secure Boot is enabled.

4

What is the likely impact if the issue is exploited?

An attacker may boot unauthorized operating system or UEFI code and potentially obtain a full loss of confidentiality, integrity, and availability of the device.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203