As reported by CISA in advisory ICSA-26-321-02, Siemens has disclosed two high-severity vulnerabilities in its .NET Client Library for SIMATIC S7 Webserver API that demand immediate attention from OT security teams. The flaws — a path traversal bug and a credential exposure issue — affect critical manufacturing environments worldwide and highlight a persistent problem in industrial software: client-side trust assumptions that break down when attackers can influence server responses.
Vulnerability Summary
| CVE | CVSS | Severity | Type | Affected Versions | Patch | Active Exploitation |
|---|---|---|---|---|---|---|
| CVE-2026-85114 | 7.5 | HIGH | Path Traversal (CWE-22) | < V3.3.61 | V3.3.61+ | Not reported |
| CVE-2026-85115 | 7.5 | HIGH | Sensitive Info in Error Msg (CWE-209) | < V3.3.62 | V3.3.62+ | Not reported |
CVE-2026-85114: Path Traversal via Ticket Download Responses
The more mechanically interesting flaw is the path traversal. The library fails to properly validate filenames embedded in ticket download responses from remote servers. If an attacker can manipulate that server response — whether through a compromised PLC, a man-in-the-middle position, or a rogue webserver — they can write arbitrary files outside the intended download directory. When overwrite mode is enabled, existing application-accessible files can be replaced entirely. This is a classic server-side trust inversion: the client library assumes the server is trustworthy, but in OT environments, PLCs and their web servers are frequently the most exposed and least hardened components on the network.
The attack surface here is not the PLC itself — it is every .NET application consuming the SIMATIC S7 Webserver API client library. Any custom HMI, data collector, or maintenance tool built on this library inherits the vulnerability.
CVE-2026-85115: Plaintext PLC Restore Passwords in Error Messages
The second vulnerability is arguably the more dangerous one from a credential hygiene standpoint. The library fails to redact PLC restore passwords from HTTP exception messages. Any application logging these exceptions — and most do, by default — is writing plaintext PLC credentials to log files, error dashboards, SIEM ingestion pipelines, and potentially centralized log aggregators. An attacker with read access to logs, monitoring systems, or even crash dump repositories gains the ability to perform unauthorized restore operations on the PLC, effectively bypassing the device's integrity protections.
Why This Matters
These vulnerabilities sit at the intersection of two underappreciated OT security blind spots:
- Client library trust models: OT environments increasingly rely on API client libraries for programmatic access to PLCs, yet these libraries are rarely subjected to the same adversarial testing as the PLC firmware itself. A compromised or rogue SIMATIC S7 webserver can pivot through the client library into the engineering workstation or data historian — a lateral movement path that few network segmentation strategies account for.
- Credential leakage in diagnostic telemetry: Modern OT environments pipe logs into centralized SIEM and observability platforms. A vulnerability that writes plaintext credentials into error messages effectively broadcasts those credentials across the entire logging infrastructure. The blast radius of CVE-2026-85115 may extend far beyond the host running the library.
Critical manufacturing remains the most exposed sector, given SIMATIC S7's dominant footprint in discrete and process manufacturing globally. Any deployment using custom .NET applications to interface with S7-1500 or S7-1200 PLCs via the Webserver API should be considered affected until verified otherwise.
Shield53 Recommendations
Siemens has responded promptly with patched releases, but the real remediation burden falls on asset owners who must identify every consuming application — many of which were built years ago by contractors or internal teams no longer with the organization. This advisory is a reminder that OT vulnerability management must extend beyond firmware and into the software supply chain that surrounds it.