If You Use Siemens, Check Your Engineering Workstations: One Flaw Is Already Being Exploited
Siemens confirms active exploitation of Software Center. We also review flaws affecting WinCC, RUGGEDCOM, and SIMATIC IPC systems.

Editorial
CISA included 17 Siemens advisories in its October 22 industrial control systems security release. The number draws attention, but these advisories do not all carry the same urgency. Another fact should drive this week’s agenda: Siemens confirmed active exploitation of a vulnerability in Software Center, an application that may be installed on engineering workstations and computers used to manage industrial software.
The priority, therefore, is not to deploy 17 updates at once. It is to identify where Software Center is installed, determine whether there is evidence of compromise, and then prioritize the WinCC, RUGGEDCOM, and SIMATIC IPC remediations according to their presence and function within the plant. This edition summarizes the actions teams can begin today without losing sight of process availability.
View CISA’s advisory release →
Vulnerabilities of the Week
[ACTIVE EXPLOITATION] Siemens Software Center Is Being Used to Run Malicious Code
Siemens confirmed active exploitation of CVE-2026-110936, a DLL side-loading vulnerability in Siemens Software Center. Attackers distributed a legitimate, signed copy of the application alongside malicious files. The Siemens program itself was not modified and, according to the vendor, its systems and update channels were not compromised. The abuse involved packages distributed outside official channels.
All versions earlier than 4.0.9.8 are affected. Existing installations should update automatically the next time the application starts. The observed activity also leaves indicators defenders can search for: “SiemensSoftwareCenter.exe” running from “AppData\Local\Programs”, a directory named “SM Software Provisioning Service”, files named “activate.bak” or “statinfosta.DB”, and connections to infrastructure published by Siemens.
View Siemens’ analysis and indicators →
Suggested action: Locate Software Center on engineering workstations, support servers, and administration computers. Confirm that they are running version 4.0.9.8 or later and that the software came from an official source. Search for the indicators published by Siemens across EDR, DNS, proxy, and firewall logs. If you find a match, isolate the computer and activate your incident response process before removing files or persistence mechanisms.
[HIGH] WinCC Can Execute Host Commands When an Attacker Already Has Database Access
CVE-2026-59241 affects the database role in several SIMATIC WinCC versions. An authenticated remote attacker with database access can escalate privileges and execute commands on the server operating system. The authentication requirement reduces exposure to a direct attack from the Internet, but the impact can be high if an account with database access has already been compromised.
WinCC V8.0 should be updated to Update 11 or later, and WinCC V8.1 to Update 7 or later. Siemens states that no fix is currently available for WinCC V7.5.
Suggested action: Inventory all WinCC instances and their versions. Restrict network access to the database, review the accounts and roles that can connect to it, and search for unusual commands or processes originating from the WinCC service. Schedule the V8.0 and V8.1 updates. For V7.5, compensate for the lack of a patch with segmentation, least privilege, and enhanced monitoring.
[HIGH/CRITICAL] RUGGEDCOM CROSSBOW and SAC Concentrate Risk at the Remote-Access Layer
RUGGEDCOM CROSSBOW contains 11 vulnerabilities that may allow SQL injection, credential exposure, privilege escalation, and unauthorized configuration changes. The advisory has a maximum CVSS v3.1 score of 8.8 and affects versions earlier than 6.0.
RUGGEDCOM CROSSBOW Station Access Controller (SAC) has a separate advisory covering vulnerabilities inherited from SQLite. Its maximum severity is critical, with a CVSS v3.1 score of 9.8. It also affects versions earlier than 6.0. In both cases, Siemens recommends updating to version 6.0 or later.
View the CROSSBOW SAC advisory →
Suggested action: Identify CROSSBOW servers and SAC controllers, confirm their versions, and prioritize their updates. Until the work is complete, allow access to their interfaces only from a controlled management network, review privileged accounts, and look for queries, access attempts, or configuration changes outside normal patterns.
[HIGH] Some SIMATIC IPCs Trust Systems Signed with a Test Key
CVE-2026-72895 affects the UEFI Secure Boot key database in several SIMATIC IPC models. A test key in the database may allow an attacker to boot an operating system or UEFI application signed with that key even when Secure Boot is enabled. Exploitation requires physical or administrative access to the computer and user involvement, so the risk depends heavily on how each IPC is protected.
The fixed versions are 28.01.15 or later for IPC227G, IPC277G, IPC277G PRO, IPC327G, and IPC377G; 31.01.13 or later for IPC BX-21A; and 1.1.4 or later for IPC RW-543A.
Suggested action: Check the model and BIOS version of every SIMATIC IPC. After installing the corrected version, load the BIOS default settings. If Secure Boot keys had already been provisioned, they must be provisioned again. Maintain physical and administrative access controls while scheduling the work.
Every update in an OT environment should be validated with the vendor, tested in a controlled environment, and carried out through the organization’s change-management process and approved maintenance windows.
Follow-up and Brief Advisories
-
S7-1500 web server: This is the same group of vulnerabilities discussed in the previous edition. The scenario requires an authorized user with permission to read diagnostics to import a malicious trace file. The code would run in the user’s browser and could perform actions on the PLC within that session’s permissions. Disable the web server if it is unnecessary. If you use it, restrict access and do not import files from unverified sources. View SSA-591731 →
-
Industrial Edge App Publisher: Versions earlier than 1.27.9 contain a vulnerability chain combining improper certificate validation with unescaped content. Exploitation requires an attacker who can intercept the communication and user interaction. Update to version 1.27.9 or later. View SSA-968435 →
-
APOGEE, TALON, and Desigo PXC/PXM: Several vulnerabilities may cause a denial of service. TALON TC Compact and Modular should be updated to 3.5.7 or later. Siemens does not plan fixes for some APOGEE and Desigo models; it recommends disabling FTP/Web services when unnecessary and placing controllers behind properly configured firewalls or gateways. View SSA-333035 →
-
PHP2Shell: Siemens and Johnson Controls published guidance concerning two remote-code-execution vulnerabilities in PHP. Before assuming that a device is vulnerable simply because it comes from either vendor, confirm the product, its version, and whether it includes an affected PHP release. View Siemens’ information → · View Johnson Controls advisories →
Closing Thoughts
This week’s order of work is clear. First, find Siemens Software Center and rule out compromise because active exploitation has been confirmed. Next, prioritize WinCC and RUGGEDCOM according to their exposure and operational role. Finally, schedule the SIMATIC IPC BIOS corrections during a controlled maintenance window.
The volume of advisories is useful for maintaining the asset and vulnerability inventory, but it should not determine urgency on its own. Observed exploitation, the actual path to the asset, and the potential impact on the process are better criteria for deciding what to address first. If you would like to compare this prioritization with your plant architecture, reply to this email and we will be glad to review it with you.
The analysis and prioritization expressed in Perímetro are the editorial responsibility of Roberto Manzo. This newsletter does not replace technical advice tailored to your organization.
