Back to Intelligence

CVE-2026-58114: Siemens SIMATIC Authentication Bypass — ICS/OT Defense and Remediation Guide

SA
Security Arsenal Team
November 17, 2026
15 min read

CISA has published ICS Advisory ICSA-26-321-08 covering an authentication bypass vulnerability (CVE-2026-58114) affecting multiple Siemens SIMATIC products. The flaw allows an on-path attacker — an adversary positioned between a legitimate user and the target system — to hijack an active session and execute arbitrary code with the victim's privileges.

Siemens is preparing fixes and has issued specific mitigations for products where patches are not yet available. The affected product list is broad, spanning both the batch management and historian tiers as well as the HMI/SCADA layer of the SIMATIC portfolio. This is not a theoretical concern — SIMATIC systems are deployed across pharmaceutical manufacturing, food and beverage production, energy, and critical infrastructure worldwide. If you run Siemens automation in your environment, treat this advisory as actionable today.

The official advisory is available here: https://www.cisa.gov/news-events/ics-advisories/icsa-26-321-08


Affected Products and Versions

The following Siemens SIMATIC products and versions are confirmed affected by CVE-2026-58114:

ProductVersionCVE
SIMATIC BATCHV9.1 (all versions)CVE-2026-58114
SIMATIC Information Server2020 (all versions)CVE-2026-58114
SIMATIC Information Server2022 (all versions)CVE-2026-58114
SIMATIC PCS 7V9.1 (all versions)CVE-2026-58114
SIMATIC Process Historian2020 (all versions)CVE-2026-58114
SIMATIC Process Historian2022 (all versions)CVE-2026-58114
SIMATIC WinCC Runtime ProfessionalV17 (all versions)CVE-2026-58114

This spans the core components of a SIMATIC PCS 7 and WinCC-based process control environment: the batch management layer (SIMATIC BATCH), the operator station runtime (WinCC Runtime Professional), the central process data repository (Process Historian), and the reporting/information layer (Information Server). A compromise in any one of these components can cascade into visibility, integrity, and availability failures across the entire control loop.


Technical Analysis: How the Attack Works

Vulnerability Class: Authentication Bypass via On-Path Session Hijacking

CVE-2026-58114 is an authentication bypass vulnerability that can be exploited by an on-path attacker — an adversary who has positioned themselves between a legitimate user and the SIMATIC application server, either through ARP poisoning, rogue gateway, compromised network infrastructure, or a malicious internal host.

The attack chain, as understood from the advisory:

  1. Legitimate user initiates a session — An operator, engineer, or administrator authenticates to a SIMATIC application (WinCC Runtime Professional, Process Historian, Information Server, or PCS 7 engineering station).
  2. Attacker intercepts the session — From the on-path position, the adversary observes or intercepts the session token, cookie, or authentication state associated with the legitimate connection.
  3. Authentication is bypassed — The attacker reuses or replays the session credential to impersonate the victim without needing to know the password or possess valid credentials.
  4. Arbitrary code execution — With the victim's session privileges, the attacker executes arbitrary code on the SIMATIC system. Depending on the victim's role, this could include operator-level commands, engineering modifications to the process logic, or full system compromise.

Why This Matters in ICS/OT Environments

This vulnerability class is particularly dangerous in OT environments for several reasons:

  • SIMATIC systems often run with elevated privileges — Process Historian and PCS 7 engineering stations frequently operate under service accounts with broad access to the underlying operating system and the process network.
  • Session integrity is the backbone of operator trust — WinCC Runtime Professional sessions drive operator HMI panels, alarms, and process control commands. A hijacked session means an attacker can issue commands, suppress alarms, or manipulate process variables as if they were the legitimate operator.
  • On-path attacks are a classic lateral movement target — Once an attacker has a foothold in the IT network or a converged IT/OT segment, on-path interception of OT management traffic is a well-documented technique for escalating into the control environment.

Exploitation Status

As of the advisory date, Siemens is preparing fixes. There is no confirmed public PoC or in-the-wild exploitation reported in the advisory. However, the advisory's existence and the specificity of the affected product list indicate that this vulnerability is known to be reachable and exploitable. Treat it as pre-exploitation — the window to apply mitigations before weaponization is now.


Detection and Response

The following content targets detection of session hijacking and subsequent malicious code execution in SIMATIC environments. These rules and queries are designed to be high-signal in an OT context where legitimate SIMATIC traffic patterns are well understood.

Sigma Rules

The first rule detects suspicious process execution patterns on SIMATIC hosts — specifically, unexpected child processes spawned by SIMATIC service executables, which would be anomalous in a properly configured OT environment where these services do not launch interactive shells or administrative tools. The second rule targets network-level detection of on-path interception indicators.

YAML
---
title: SIMATIC Service Spawning Suspicious Child Process
id: a1b2c3d4-5e6f-7890-abcd-ef1234567890
status: experimental
description: Detects SIMATIC WinCC, PCS 7, Process Historian, or Information Server service executables spawning unexpected child processes such as cmd.exe, powershell.exe, or wscript.exe — indicative of post-exploitation code execution following session hijacking.
references:
  - https://www.cisa.gov/news-events/ics-advisories/icsa-26-321-08
  - https://attack.mitre.org/techniques/T1059/
author: Security Arsenal
date: 2026/11/18
tags:
  - attack.execution
  - attack.t1059.003
  - attack.t1059.001
logsource:
  category: process_creation
  product: windows
detection:
  selection_parent:
    ParentImage|contains:
      - '\\wincc'
      - '\\pcs7'
      - '\\simatic'
      - '\\siemens'
      - '\\ccprojectmgr'
      - '\\phserver'
      - '\\infoserver'
  selection_child:
    Image|endswith:
      - '\\cmd.exe'
      - '\\powershell.exe'
      - '\\pwsh.exe'
      - '\\wscript.exe'
      - '\\cscript.exe'
      - '\\mshta.exe'
      - '\\rundll32.exe'
      - '\\regsvr32.exe'
      - '\\wmic.exe'
      - '\\net.exe'
      - '\\net1.exe'
      - '\\sc.exe'
  condition: selection_parent and selection_child
falsepositives:
  - Legitimate SIMATIC administrative maintenance windows (document and suppress)
  - Siemens engineering tools that legitimately invoke subprocesses during project deployment
level: high
---
title: Unexpected SMB or RDP Connection to SIMATIC Process Historian or Information Server
id: b2c3d4e5-6f78-9012-bcde-f12345678901
status: experimental
description: Detects inbound SMB or RDP connections to SIMATIC Process Historian or Information Server hosts from unexpected source IPs — potential indicator of lateral movement or on-path attacker staging.
references:
  - https://www.cisa.gov/news-events/ics-advisories/icsa-26-321-08
  - https://attack.mitre.org/techniques/T1021/
author: Security Arsenal
date: 2026/11/18
tags:
  - attack.lateral_movement
  - attack.t1021.001
  - attack.t1021.002
logsource:
  category: network_connection
  product: windows
detection:
  selection_destination:
    DestinationIp|contains:
      - '10.1.100.'
      - '10.1.101.'
  selection_port:
    DestinationPort:
      - 445
      - 3389
  selection_image:
    Image|endswith:
      - '\\svchost.exe'
      - '\\System'
  condition: selection_destination and selection_port and selection_image
falsepositives:
  - Legitimate engineering workstation access during maintenance
  - Authorized remote support connections (whitelist known source IPs)
level: medium
---
title: Suspicious Session Token Reuse — Multiple Source IPs for Same User
id: c3d4e5f6-7890-1234-cdef-123456789012
status: experimental
description: Detects authentication events where a single user account is associated with multiple distinct source IP addresses within a short timeframe — potential indicator of session hijacking or token replay.
references:
  - https://www.cisa.gov/news-events/ics-advisories/icsa-26-321-08
  - https://attack.mitre.org/techniques/T1563/
author: Security Arsenal
date: 2026/11/18
tags:
  - attack.defense_evasion
  - attack.t1563.002
logsource:
  category: authentication
  product: windows
detection:
  selection:
    LogonType:
      - 3
      - 10
  filter_known_ots:
    TargetUserName|contains:
      - 'SIMATIC'
      - 'PCS7'
      - 'WINCC'
  condition: selection and filter_known_ots
falsepositives:
  - Users with multiple thin clients or VDI sessions
  - Load-balanced application front-ends
level: medium

Microsoft Sentinel / Defender KQL Hunt Query

The following KQL query hunts across endpoint and network telemetry ingested into Microsoft Sentinel. It targets process execution anomalies on SIMATIC hosts, unexpected network connections, and authentication patterns consistent with session hijacking. This assumes you are ingesting Windows Security Events, Sysmon, and/or Defender for Endpoint data via the standard connectors.

KQL — Microsoft Sentinel / Defender
// Hunt: SIMATIC Session Hijacking and Post-Exploitation Indicators
// Author: Security Arsenal
// Date: 2026-11-18
// Description: Queries for suspicious process execution, network connections, and authentication anomalies
// on hosts running Siemens SIMATIC products affected by CVE-2026-58114.

// Step 1: Identify SIMATIC-related processes spawning suspicious children
let suspiciousChildren = dynamic(["cmd.exe","powershell.exe","pwsh.exe","wscript.exe","cscript.exe","mshta.exe","rundll32.exe","regsvr32.exe","wmic.exe","net.exe","net1.exe","sc.exe"]);
let simaticParents = dynamic(["wincc","pcs7","simatic","siemens","ccprojectmgr","phserver","infoserver","rtserver","batch"]);
DeviceProcessEvents
| where TimeGenerated > ago(7d)
| where InitiatingProcessFileName has_any (simaticParents)
   or InitiatingProcessFolderPath has_any (simaticParents)
| where FileName has_any (suspiciousChildren)
| project TimeGenerated, DeviceName, InitiatingProcessFileName, InitiatingProcessCommandLine,
          FileName, ProcessCommandLine, AccountName, AccountDomain, RemoteIP, RemotePort
| order by TimeGenerated desc;

// Step 2: Hunt for unexpected network connections to SIMATIC hosts
let simaticHosts = dynamic(["10.1.100.","10.1.101.","10.1.102."]);
DeviceNetworkEvents
| where TimeGenerated > ago(7d)
| where RemoteIP has_any (simaticHosts)
   or LocalIP has_any (simaticHosts)
| where RemotePort in (445, 3389, 1433, 1434, 8080, 443, 80)
| where InitiatingProcessFileName !in ("svchost.exe","System","lsass.exe")
   and InitiatingProcessFileName !has_any ("siemens","simatic","wincc","pcs7")
| project TimeGenerated, DeviceName, LocalIP, LocalPort, RemoteIP, RemotePort,
          InitiatingProcessFileName, InitiatingProcessCommandLine, RemoteUrl
| order by TimeGenerated desc;

// Step 3: Detect concurrent logons from multiple source IPs for the same user
SecurityEvent
| where TimeGenerated > ago(24h)
| where EventID == 4624
| where LogonType in (3, 10)
| where TargetUserName has_any ("SIMATIC","PCS7","WINCC","BATCH","HISTORIAN")
   or TargetUserName has_any ("operator","engineer","admin")
| summarize SourceIPs = dcount(IpAddress), IPList = make_set(IpAddress),
           FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated)
           by TargetUserName, TargetDomainName, Computer
| where SourceIPs > 1
| project TargetUserName, TargetDomainName, Computer, SourceIPs, IPList, FirstSeen, LastSeen
| order by SourceIPs desc;

Velociraptor VQL Hunt

The following VQL artifact hunts for process execution anomalies and network connection indicators on endpoints running SIMATIC software. It targets the same behaviors as the Sigma rules but provides the endpoint forensics context needed for incident scoping.

VQL — Velociraptor
-- Hunt: SIMATIC CVE-2026-58114 — Suspicious Process and Network Indicators
-- Author: Security Arsenal
-- Date: 2026-11-18
-- Description: Identifies suspicious child processes spawned by SIMATIC service executables
-- and unexpected network connections on affected hosts.

LET simatic_procs = pslist()
WHERE Name =~ '(?i)(wincc|pcs7|simatic|siemens|ccprojectmgr|phserver|infoserver|rtserver|batch)'

LET suspicious_children = pslist()
WHERE Name =~ '(?i)(cmd|powershell|pwsh|wscript|cscript|mshta|rundll32|regsvr32|wmic|net\.exe|net1|sc\.exe)'
  AND Ppid IN (SELECT Pid FROM simatic_procs)

SELECT suspicious_children.Pid AS ChildPid,
       suspicious_children.Name AS ChildName,
       suspicious_children.CommandLine AS ChildCmdLine,
       suspicious_children.Username AS ChildUser,
       suspicious_children.CreateTime AS ChildCreated,
       simatic_procs.Pid AS ParentPid,
       simatic_procs.Name AS ParentName,
       simatic_procs.CommandLine AS ParentCmdLine
FROM suspicious_children
JOIN simatic_procs ON suspicious_children.Ppid = simatic_procs.Pid

Remediation Script

The following PowerShell script checks whether the affected SIMATIC products are installed on a Windows host and verifies whether they are running. It does not apply patches (as Siemens fixes are pending) but enables defenders to inventory exposure and enforce network-level mitigations.

PowerShell
#Requires -RunAsAdministrator
<#
.SYNOPSIS
  Security Arsenal — CVE-2026-58114 SIMATIC Exposure Assessment
.DESCRIPTION
  Checks for installed and running Siemens SIMATIC products affected by
  the authentication bypass vulnerability (CVE-2026-58114). Provides
  inventory, running service status, and network connection audit.
  Use this to scope your exposure and prioritize mitigations.
.AUTHOR
  Security Arsenal
.DATE
  2026-11-18
#>

Write-Host "=" * 70
Write-Host "CVE-2026-58114 — Siemens SIMATIC Exposure Assessment"
Write-Host "=" * 70

# --- Step 1: Inventory installed SIMATIC products ---
Write-Host "`n[STEP 1] Scanning for installed SIMATIC products..."
$simaticProducts = @(
    "SIMATIC BATCH",
    "SIMATIC Information Server",
    "SIMATIC PCS 7",
    "SIMATIC Process Historian",
    "SIMATIC WinCC Runtime Professional",
    "SIMATIC WinCC",
    "SIMATIC NET"
)

$installed = Get-WmiObject -Class Win32_Product -ErrorAction SilentlyContinue |
    Where-Object { $p = $_.Name; $simaticProducts | Where-Object { $p -like "*$_*" } } |
    Select-Object Name, Version, InstallDate

if ($installed) {
    Write-Host "  [ALERT] The following SIMATIC products are installed:"
    $installed | Format-Table -AutoSize
} else {
    Write-Host "  [OK] No SIMATIC products detected in Win32_Product."
}

# Also check via registry (faster and more reliable)
$regPaths = @(
    "HKLM:\SOFTWARE\Siemens",
    "HKLM:\SOFTWARE\WOW6432Node\Siemens"
)
foreach ($path in $regPaths) {
    if (Test-Path $path) {
        Write-Host "  [INFO] Found Siemens registry key: $path"
        Get-ChildItem $path -ErrorAction SilentlyContinue | ForEach-Object {
            Write-Host "    - $($_.PSChildName)"
        }
    }
}

# --- Step 2: Check for running SIMATIC services ---
Write-Host "`n[STEP 2] Checking for running SIMATIC services..."
$simaticServices = Get-Service -ErrorAction SilentlyContinue |
    Where-Object { $_.DisplayName -like "*SIMATIC*" -or $_.DisplayName -like "*WinCC*" -or $_.DisplayName -like "*PCS 7*" -or $_.DisplayName -like "*Siemens*" -or $_.DisplayName -like "*Process Historian*" }

if ($simaticServices) {
    Write-Host "  [ALERT] The following SIMATIC-related services are running:"
    $simaticServices | Where-Object { $_.Status -eq "Running" } |
        Format-Table Name, DisplayName, Status, StartType -AutoSize
} else {
    Write-Host "  [OK] No SIMATIC services found."
}

# --- Step 3: Audit network connections on SIMATIC-relevant ports ---
Write-Host "`n[STEP 3] Auditing network connections..."
$simaticPorts = @(80, 443, 1433, 1434, 445, 3389, 8080, 4840, 102, 502, 20000)
$connections = Get-NetTCPConnection -State Listen -ErrorAction SilentlyContinue |
    Where-Object { $simaticPorts -contains $_.LocalPort } |
    Select-Object LocalAddress, LocalPort, OwningProcess

if ($connections) {
    Write-Host "  [INFO] Listening on the following ports commonly used by SIMATIC/OT:"
    foreach ($conn in $connections) {
        $proc = Get-Process -Id $conn.OwningProcess -ErrorAction SilentlyContinue
        Write-Host "    - $($conn.LocalAddress):$($conn.LocalPort)  (PID $($conn.OwningProcess): $($proc.ProcessName))"
    }
} else {
    Write-Host "  [OK] No listening connections on common SIMATIC/OT ports."
}

# --- Step 4: Check for unexpected child processes ---
Write-Host "`n[STEP 4] Checking for suspicious child processes of SIMATIC services..."
$simaticProcs = Get-Process -ErrorAction SilentlyContinue |
    Where-Object { $_.ProcessName -match "(wincc|pcs7|simatic|siemens|ccprojectmgr|phserver|infoserver|rtserver|batch)" }

if ($simaticProcs) {
    $suspiciousChildren = Get-WmiObject Win32_Process -ErrorAction SilentlyContinue |
        Where-Object { $_.ParentProcessId -in $simaticProcs.Id } |
        Where-Object { $_.Name -match "(cmd|powershell|pwsh|wscript|cscript|mshta|rundll32|regsvr32|wmic|net\.exe|net1|sc\.exe)" }

    if ($suspiciousChildren) {
        Write-Host "  [CRITICAL] Suspicious child processes detected!"
        $suspiciousChildren | Format-Table ProcessId, ParentProcessId, Name, CommandLine -AutoSize
        Write-Host "  [ACTION] Investigate immediately — this may indicate active exploitation."
    } else {
        Write-Host "  [OK] No suspicious child processes detected under SIMATIC services."
    }
} else {
    Write-Host "  [OK] No SIMATIC processes running."
}

# --- Step 5: Network segmentation check ---
Write-Host "`n[STEP 5] Checking network adapters for IT/OT segmentation..."
Get-NetIPAddress -AddressFamily IPv4 -ErrorAction SilentlyContinue |
    Where-Object { $_.InterfaceAlias -notlike "*Loopback*" } |
    Format-Table InterfaceAlias, IPAddress, PrefixLength -AutoSize

Write-Host "`n" + "=" * 70
Write-Host "Assessment complete. Review output and apply Siemens mitigations."
Write-Host "Reference: https://www.cisa.gov/news-events/ics-advisories/icsa-26-321-08"
Write-Host "=" * 70

Remediation and Mitigation

Siemens is preparing fixes for CVE-2026-58114. Until patches are available, apply the following mitigations immediately. These align with Siemens' recommendations and established ICS/OT security best practices.

Immediate Actions (No Patch Required)

  1. Enforce network segmentation — Isolate SIMATIC systems from the corporate IT network and the internet. Place affected systems (WinCC Runtime Professional, Process Historian, Information Server, PCS 7) behind a firewall with strict ACLs. Block all unnecessary inbound connections, especially from untrusted segments.
  2. Restrict on-path positioning — Prevent attackers from gaining a man-in-the-middle position:
    • Implement 802.1X port-based network access control on OT switch ports.
    • Deploy static ARP entries or Dynamic ARP Inspection (DAI) on switches to prevent ARP spoofing.
    • Disable unused switch ports and enforce MAC address filtering where operationally feasible.
  3. Limit remote access — If remote access to SIMATIC systems is required, use VPN with multi-factor authentication (MFA) and restrict connections to specific, whitelisted source IPs. Never expose SIMATIC management interfaces directly to the internet or to untrusted internal segments.
  4. Monitor authentication patterns — Enable and centralize logging for authentication events on SIMATIC hosts. Alert on concurrent logons from multiple source IPs, logons outside of normal operating hours, and authentication failures followed by successful logons from different sources.
  5. Harden SIMATIC service accounts — Ensure SIMATIC service accounts run with least privilege. Remove local administrator rights from service accounts where possible. Use Group Managed Service Accounts (gMSA) or dedicated low-privilege accounts for SIMATIC services.
  6. Deploy application whitelisting — On SIMATIC hosts (especially Process Historian and Information Server), implement application whitelisting (e.g., Windows AppLocker, Microsoft WDAC) to prevent unauthorized executables from running, even if an attacker gains code execution via session hijacking.

Network-Level Protections

  • Block unnecessary ports on the OT firewall between SIMATIC segments. Specifically, restrict access to SIMATIC management interfaces (typically HTTP/HTTPS, SQL Server, OPC UA) to authorized engineering workstations only.
  • Enable encrypted transport where supported. If SIMATIC products support TLS or OPC UA with encryption, enforce it. While this does not directly remediate the authentication bypass, it raises the bar for on-path interception.
  • Deploy network intrusion detection — Monitor OT network traffic for anomalies such as unexpected ARP replies, duplicate MAC addresses, and unusual session establishment patterns. Tools like Zeek (formerly Bro) with ICS protocol analyzers, or dedicated OT security platforms, can detect on-path attack indicators.

Vendor Patching

  • Monitor the Siemens ProductCERT advisory for patch releases. Siemens publishes security advisories at https://www.siemens.com/cert and through the Siemens ProductCERT portal. Subscribe to their notification service if you have not already.
  • Test patches in a lab environment before deploying to production OT systems. SIMATIC environments are sensitive to downtime — validate patch compatibility with your specific project configuration.
  • Apply patches during scheduled maintenance windows following your organization's change management process for OT systems.

CISA Recommendations

CISA's ICS advisory (ICSA-26-321-08) reiterates standard defensive measures for ICS environments:

  • Minimize network exposure for all control system devices and ensure they are not accessible from the internet.
  • Locate control system networks and remote devices behind firewalls and isolate them from business networks.
  • Use secure methods for remote access — VPNs with MFA, and only when necessary.

Key Takeaways for Defenders

  1. CVE-2026-58114 is a session hijacking vulnerability, not a remote code execution bug in the traditional sense. The attacker must be on-path — this means your network segmentation and switch-level security controls are your first and most effective line of defense.
  2. Inventory your exposure now. Use the provided PowerShell script to identify which SIMATIC products are installed and running in your environment. You cannot protect what you do not know about.
  3. Detection should focus on behavioral anomalies. The Sigma rules and KQL queries provided target post-exploitation indicators (suspicious child processes, unexpected network connections, concurrent logons) rather than the exploitation attempt itself, which occurs at the network layer and may not generate endpoint telemetry.
  4. This is a pre-exploitation window. Siemens is preparing fixes. Apply mitigations today, monitor for patch releases, and validate patches in a test environment before production deployment.
  5. If you cannot patch immediately, compensate with network controls. The vulnerability requires an on-path position. If an attacker cannot position themselves between the user and the SIMATIC system, the vulnerability is not exploitable. Network segmentation, port security, and encrypted transport are your compensating controls.

Related Resources

Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.