Siemens patches part of CVE-2026-111497 IEM exposure
The advisory leaves Common Configurator users on mitigations, which is not the same thing as a finished remediation path.
TL;DR
CISA republished Siemens ProductCERT SSA-443410 on CVE-2026-111497, a critical Brotli buffer overflow affecting multiple Industrial Edge Management components in critical manufacturing deployments worldwide. Siemens lists fixes for several configurators and central cloud services, but Common Configurator on IEM and on Edge still have no fix. Those users are left with firewall or WAF controls, application removal, or stopping the affected component until Siemens ships more.
CISA’s November 12 advisory on Siemens Industrial Edge Management is not a clean patch notice. Siemens has released updated versions for Cloud Connector Configurator, Data Flow Monitoring, Databus Configurator, DataXess Configurator, Edge OPC UA Server Configurator, and Flow Creator Configurator, and says the vulnerability was fixed on the central cloud service for Industrial Edge Management Cloud and Industrial Edge Hub. That’s the easy half.
The hard half is Common Configurator. For Common Configurator on IEM and Common Configurator on Device, Siemens lists all versions as affected and says no fix is currently available. The stated mitigations are to uninstall all Management Applications and protect the IEM instance with a firewall or Web Application Firewall, or to stop Common Configurator on Device until a fix is available. That is operationally different from applying a versioned update and closing a ticket.
The underlying issue is CVE-2026-111497, described as a buffer overflow in the Brotli decoder in Google Brotli versions 1.0.3 through 1.2.0. CISA’s republished advisory gives it a CVSS 3.1 score of 9.8 and says a remote unauthenticated attacker could corrupt adjacent decoder state memory, disclose sensitive memory, cause denial of service, or potentially execute arbitrary code with a crafted Brotli-compressed stream. Siemens also says that if no Management Applications are installed, no action is required because the affected functionality is not used or exposed.
For organizations running affected IEM components in critical manufacturing environments, the practical sequence is blunt: update the components that have fixed versions, verify whether Management Applications or Device Applications are installed, and document any remaining compensating controls for Common Configurator. The open item isn't risk theory. It’s the missing fix date for the components where the current answer is still workaround, not remediation.
Published ·Deep Fathom