CISA Recommends SQL Encryption for Siemens SIMATIC NTLM Relay Exposure
Quick Answer
Review the listed SIMATIC product lines and implement Siemens’ SQL Server communication-encryption mitigation after compatibility testing.
Confirm Scope And Apply The Supported Remediation
What to do now: Record exact SIMATIC product lines, SQL Server endpoints, authentication flows, encryption configuration and operational dependencies. An attacker must achieve an on-path position to relay authentication. Assess reachable services and account permissions rather than assuming every listed installation permits code execution. Follow the SQL encryption procedure linked from ICSA-26-321-08 and the product documentation. Restrict unnecessary service reachability while planning and testing the change. Confirm encrypted SQL connections from every relevant client and test historian, reporting and operator workflows. Retain certificate, connection-policy, application-test and exception evidence.
Last verified: 2026-11-17 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Listed SIMATIC engineering, historian and runtime product lines |
|---|---|
| Advisory | ICSA-26-321-08 |
| CVE | CVE-2026-58114 |
| Authoritative release date | 2026-11-17T12:00:00Z — CISA release timestamp in the advisory page. |
| Authority revision date | No separate material revision is confirmed for this CISA release. |
| Affected versions | SIMATIC BATCH V9.1; Information Server 2020 and 2022; PCS 7 V9.1; Process Historian 2020 and 2022; WinCC Runtime Professional V17, V18, V19, V20 and V21; WinCC V7.5, V8.0 and V8.1. |
| Fixed version | No fixed version is listed; manually configure SQL Server communication encryption using the Siemens procedure |
| CVSS base score | 7.5 (CVSS v3.1) |
| CVSS severity | High |
| Exploitation status | The cited CISA ICS advisory does not confirm exploitation of these products in the wild.; no exploitation claim is inferred. |
What Changed
CISA describes an NTLM relay weakness that can let an on-path attacker impersonate a legitimate user. Impact depends on accessible services and the user’s privileges.
What To Validate Now
- Inventory. Record exact SIMATIC product lines, SQL Server endpoints, authentication flows, encryption configuration and operational dependencies.
- Establish applicability. An attacker must achieve an on-path position to relay authentication. Assess reachable services and account permissions rather than assuming every listed installation permits code execution.
- Remediate. Follow the SQL encryption procedure linked from ICSA-26-321-08 and the product documentation. Restrict unnecessary service reachability while planning and testing the change.
- Validate. Confirm encrypted SQL connections from every relevant client and test historian, reporting and operator workflows. Retain certificate, connection-policy, application-test and exception evidence.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
CISA lists no planned fix for BATCH V9.1, PCS 7 V9.1 and the named Information Server and Process Historian lines; WinCC entries currently have no available fix. Do not treat a mitigation as a patch or disable certificate validation to restore connectivity.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.

