HomeIntelligenceBrief
VULNERABILITY BRIEF🔴 Critical Vulnerability

Critical Zero‑Day Trilogy in Siemens ROX II OT Switches Threatens Industrial Control Networks

Three chained zero‑day vulnerabilities (CVE‑2025‑40948, CVE‑2025‑40947, CVE‑2025‑40949) in Siemens ROX II switches enable arbitrary file read, privilege escalation, and persistent root access. The flaws highlight the need for continuous control mapping and evidence collection in SOC 2‑type compliance programs.

LiveThreat™ Intelligence · 📅 July 17, 2026· 📰 unit42.paloaltonetworks.com
🔴
Severity
Critical
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
2 sector(s)
Actions
3 recommended
📰
Source
unit42.paloaltonetworks.com

Critical Zero‑Day Trilogy in Siemens ROX II OT Switches Threatens Industrial Control Networks

What Happened – Researchers from Palo Alto Networks Unit 42, in collaboration with Siemens, disclosed three chained zero‑day vulnerabilities (CVE‑2025‑40948, CVE‑2025‑40947, CVE‑2025‑40949) in Siemens ROX II operational‑technology switches. The chain enables arbitrary file read, command‑injection privilege escalation, and persistent root‑level code execution, giving an attacker full control of the device and the surrounding industrial network. Siemens has issued advisories and a firmware fix (v2.17.1).

Why It Matters for Compliance & Audit Readiness

  • The scenario exemplifies a control‑gap that SOC 2‑type programs must identify, map, and continuously monitor (e.g., CC6.1 System Operations, CC7.1 Change Management).
  • Continuous evidence collection on firmware version, patch status, and configuration drift becomes essential audit evidence.
  • Demonstrating timely remediation and documented verification satisfies the “risk mitigation” and “monitoring” criteria of SOC 2 and related regulatory frameworks.

Who Is Affected – Energy & utilities, manufacturing, and other sectors that rely on OT switches for critical‑infrastructure control.

Recommended Actions

  • Inventory all ROX II (and similar) devices and verify firmware version against Siemens SSA‑973901, SSA‑078743, SSA‑081142.
  • Apply the v2.17.1 firmware patch immediately; document the change in your configuration‑management system.
  • Enable continuous configuration‑monitoring tools that capture firmware hash and version as immutable audit logs.
  • Map the affected controls (e.g., CC6.1, CC7.1) to your SOC 2 readiness framework and collect evidence of remediation for the next audit cycle.

Source: Palo Alto Unit 42 report

Technical Notes – The exploit chain starts with an insecure xz utility configuration (CVE‑2025‑40948, CVSS 6.8), proceeds to unsanitized command injection in the feature‑key validator (CVE‑2025‑40947, CVSS 7.5), and finishes with cron‑table injection via the web‑management scheduler (CVE‑2025‑40949, CVSS 9.1). Data at risk includes configuration files, password hashes, private keys, and any process‑control data traversing the switch.

📰 Original Source
https://unit42.paloaltonetworks.com/siemens-rox-ii-zero-day-vulnerabilities/

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Trust Operations

Every gap like this maps to a control you can evidence.

The Verisq AI Trust Operations platform maps incidents to your control framework and collects the evidence continuously — so your Trust Center shows proof, not promises, when a buyer or auditor asks.

Explore the Verisq AI Trust Operations platform →