A vulnerability has been identified in SIMATIC BATCH V9.1 (All versions), SIMATIC Information Server 2020 (All versions), SIMATIC…

Check whether my systems are affected by CVE-2026-58114 (A vulnerability has been identified in SIMATIC BATCH V9.1 (All versions), SIMATIC Information Server 2020 (All versions), SIMATIC…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-58114 (entry last updated 2026-11-10):
Affected:
- Siemens SIMATIC BATCH V9.1: all versions
- Siemens SIMATIC Information Server 2020: all versions
- Siemens SIMATIC Information Server 2022: all versions
- Siemens SIMATIC PCS 7 V9.1: all versions
- Siemens SIMATIC Process Historian 2020: all versions
- Siemens SIMATIC Process Historian 2022: all versions
- Siemens SIMATIC WinCC Runtime Professional V17: all versions
- Siemens SIMATIC WinCC Runtime Professional V18: all versions
- Siemens SIMATIC WinCC Runtime Professional V19: all versions
- Siemens SIMATIC WinCC Runtime Professional V20: all versions
- and 4 more affected products, listed on https://cve.now/CVE-2026-58114
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affected products include SIMATIC BATCH V9.1, Information Server 2020/2022, PCS 7 V9.1, Process Historian 2020/2022, WinCC V7.5/V8.0/V8.1 and WinCC Runtime Professional V17-V21 (all versions). (source: https://cert-portal.siemens.com/productcert/html/ssa-970803.html)
- Remote user authentication uses the deprecated NTLM protocol and is not properly secured. (source: https://cert-portal.siemens.com/productcert/html/ssa-970803.html)
- Kerberos is not used (for example, no domain with a Server Principal Name set). (source: https://cert-portal.siemens.com/productcert/html/ssa-970803.html)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
Workaround: Manually configure the SQL Server Database for encrypting communication. (source: https://cert-portal.siemens.com/productcert/html/ssa-970803.html)
CISA KEV: CVE-2026-58114 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-58114 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://cert-portal.siemens.com/productcert/html/ssa-970803.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-58114
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-58114.