Home › Intelligence › Brief
VULNERABILITY BRIEF 🔴 Critical Vulnerability

Multiple Critical Vulnerabilities in Siemens SIDIS Prime (CVE‑2024‑29857 – CVE‑2026‑22610) Threaten Industrial Control Systems

Siemens SIDIS Prime versions prior to 4.0.800 contain 23 high‑severity bugs, including remote code execution and path‑traversal, that could let attackers disrupt or sabotage critical infrastructure. TPRM teams must verify patch status and isolate affected systems.

Verisq™ Intelligence · 📅 March 13, 2026 · 📰 cisa.gov
🔴
Severity
Critical
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
3 sector(s)
✅
Actions
5 recommended
📰
Source
cisa.gov

Multiple Critical Vulnerabilities in Siemens SIDIS Prime (CVE‑2024‑29857 – CVE‑2026‑22610) Threaten Industrial Control Systems

What It Is – Siemens SIDIS Prime (versions < 4.0.800) contains a cascade of 23 high‑severity flaws across OpenSSL, SQLite, and numerous Node.js packages. Vulnerabilities range from out‑of‑bounds reads/writes and path‑traversal to prototype‑pollution and OS‑command injection, many scoring 8.7 CVSS v3.

Exploitability – Public advisories confirm that several of the flaws are exploitable remotely without authentication. Proof‑of‑concept code for the OpenSSL and Node.js prototype‑pollution bugs has been released, and threat‑actor chatter indicates active scanning of industrial networks for vulnerable SIDIS deployments.

Affected Products – Siemens SIDIS Prime (all releases prior to 4.0.800). The product is a core SCADA/ICS platform used in water, energy, and manufacturing facilities worldwide.

TPRM Impact – A compromised SIDIS instance can give adversaries direct control of process‑control logic, enabling sabotage, data exfiltration, or ransomware deployment against downstream suppliers. Because SIDIS often integrates with third‑party PLCs and ERP systems, a breach can cascade through the supply chain, exposing partner organizations to operational downtime and regulatory penalties.

Recommended Actions –

  1. Patch Immediately – Deploy Siemens SIDIS Prime 4.0.800 or later across all environments.
  2. Inventory & Verify – Conduct an exhaustive inventory of all SIDIS instances; confirm version numbers against the advisory.
  3. Network Segmentation – Isolate SIDIS servers from corporate IT and limit inbound traffic to trusted management subnets.
  4. Monitor for Indicators – Deploy IDS/IPS signatures for the disclosed CVEs and enable logging of anomalous command‑execution attempts.
  5. Supply‑Chain Review – Re‑assess contracts with vendors that rely on SIDIS for data exchange; require proof of remediation.

Source: CISA Advisory – ICSA‑26‑071‑03

📰 Original Source
https://www.cisa.gov/news-events/ics-advisories/icsa-26-071-03 ↗

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

Vulnerability exposure

Is this CVE in your supply chain?

Verisq matches published vulnerabilities against the software your vendors run, so you know which relationships this touches before the next review.

See vendor exposure →