An industrial control workstation displays secure cloud software updates connected to factory equipment.
If your build pipeline pulls in a Siemens NuGet package to talk to a SIMATIC PLC, an advisory published today is relevant to you. Siemens ProductCERT has disclosed two vulnerabilities in the .NET Client Library for the SIMATIC S7 Webserver API. One lets a hostile server write files outside the intended download folder. The other can leak a PLC restore password into logs. CISA republished the advisory on November 17 as ICSA-26-321-02. It is a repeat of Siemens SSA-390352, which first appeared in October.

An industrial control workstation displays secure cloud software updates connected to factory equipment. What the library is, and why .NET shops should care​

The library is a .NET wrapper for the S7 PLC Webserver API. It provides methods for calling the PLC Webserver API using HttpClient. The package targets .NET Framework 4.8, .NET Standard 2.0, and .NET 8.0, 9.0, and 10.0. The package name is Siemens.Simatic.S7.Webserver.API.

That target list spans old Windows-only desktop tooling and current cross-platform .NET. The advisory doesn't name affected application types. A reasonable guess, and it is only that, is that the consumers are engineering utilities, monitoring services and deployment tools running on ordinary Windows workstations or servers. WindowsForum's earlier coverage of this advisory made the same assumption.

The two vulnerabilities​

CVE-2026-85114 is a path traversal flaw (CWE-22). Affected applications do not properly validate filenames received from remote servers during ticket downloads. An attacker who can manipulate the ticket response could write arbitrary files outside the intended download directory. When overwriting is enabled, they could replace existing files accessible to the application.

The practical risk depends on what the host application can write to. A service running with broad file permissions is a worse target than a sandboxed utility. The published CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N with high integrity impact and no confidentiality or availability impact. Siemens also gives it a CVSS 4.0 score of 8.7.

CVE-2026-85115 is a sensitive information leak in error messages (CWE-209). Affected applications do not properly redact PLC restore passwords from HTTP error exception messages. An attacker with access to logs or other diagnostic output could obtain the plaintext restore password and potentially perform unauthorized operations on the PLC. Its CVSS 3.1 score is 5.5 (Medium), with a local attack vector and low privileges required. Its CVSS 4.0 score is 6.8.

The headline 7.5 and 8.7 scores belong to the path traversal issue. The password leak is scored lower, but in a plant it can matter more. Exception text tends to flow into log files, ticketing systems, crash dumps and monitoring platforms that many people can read.

Version thresholds: 3.3.61 is not enough​

Siemens lists a separate fix threshold for each CVE:

VulnerabilityAffected versionsFixed in
CVE-2026-85114Below 3.3.613.3.61 or later
CVE-2026-85115Below 3.3.623.3.62 or later

A project that stops at 3.3.61 therefore fixes the path traversal but is still in the affected range for the password leak. CISA's summary line lists both thresholds, which is easy to misread. Target 3.3.62 or later to cover both CVEs, after your usual compatibility testing. The advisory offers no workaround that replaces upgrading.

What to do​

  1. Find the dependency. Search your repositories, solution files and deployment artifacts for Siemens.Simatic.S7.Webserver.API. Check transitive references as well as direct ones.
  2. Check the version actually deployed. The version in a project file may not match what shipped. Look at build output, packaged releases and server images.
  3. Upgrade to 3.3.62 or later. The NuGet gallery shows the standard .NET CLI form, dotnet add package Siemens.Simatic.S7.Webserver.API --version <version>. Rebuild, test against your PLC firmware, and redeploy.
  4. Review logs for the password. Siemens does not prescribe a rotation procedure. It is still sensible to check who can read logs and diagnostics from older builds, and to treat any exposed restore password under your normal credential-handling process. That is our recommendation, not Siemens'.
  5. Constrain the file-write blast radius. Run applications that download tickets with the least file-system privilege they need. Consider whether overwriting really needs to be enabled. The advisory says overwriting makes the traversal more damaging.

What is not known​

  • No exploitation is reported. The advisory describes what an attacker could do. It reports no attacks in the wild and gives no indicators of compromise. One tracker lists the KEV status as "No", meaning the flaw is not in CISA's Known Exploited Vulnerabilities catalog.
  • No PLC models are named. The vulnerable component is the client library, not the PLC firmware.
  • The attack preconditions are narrow but real. The traversal needs an attacker who can manipulate the ticket response, which implies a malicious or compromised server or a man-in-the-middle position. The GitHub README shows a certificate callback example that accepts any certificate. In an app that copies that snippet, a network attacker would have an easier time. That is our inference, not a claim in the advisory.

Industrial security context​

Siemens repeats its standard advice. Protect network access to devices, and configure the environment according to its Industrial Security operational guidelines. CISA's recommended practices add the usual list:

  • Keep control systems off the internet.
  • Put them behind firewalls and isolate them from business networks.
  • Use maintained VPNs for remote access, while remembering that a VPN is only as secure as the devices connected to it.
  • Run an impact analysis before deploying defensive changes.

These measures reduce exposure but do not replace the patch.

The advisory lists Critical Manufacturing as the affected sector and says the product is deployed worldwide. Siemens credits Liyander Rishwanth L. with coordinated disclosure.

The timeline​

Siemens published the advisory on October 13, 2026. On November 10 it added the researcher acknowledgement. CISA's November 17 posting is, in its own words, a verbatim republication of Siemens ProductCERT SSA-390352. It adds no new technical findings. If your team patched in October, the republication changes nothing. If you missed the first notice, it is a prompt to audit your dependencies now.

This is a small library with two modest-sounding bugs. But a path traversal flaw and a leaked credential next to PLC infrastructure are the kind of problem that spreads once it is buried in a build output nobody checks. Do the audit, and aim for 3.3.62.

 

References

  1. Siemens .NET Client Library for SIMATIC S7 Webserver API CISA 2026-11-17T12:00:00+00:00
  2. GitHub - siemens/simatic-s7-webserver-api: A .NET API Client Library for the SIMATIC S7 PLC Webserver API · GitHub github.com
  3. CVE-2026-85114: .NET Client Library for SIMATIC S7 Webserver… strix.ai