Home › Intelligence › Brief
VULNERABILITY BRIEF 🟠 High Vulnerability

Path Traversal and Sensitive Info Leak in Siemens SIMATIC S7 Webserver API .NET Client Library (CVE‑2026‑85114/85115)

Two CVEs (CVE‑2026‑85114, CVE‑2026‑85115) affect Siemens' SIMATIC S7 Webserver API .NET client library, enabling path‑traversal file writes and error‑message disclosure. The flaws underscore the importance of continuous component‑risk monitoring and demonstrable secure‑configuration controls for audit readiness.

Verisq™ Intelligence · 📅 October 23, 2026 · 📰 cisa.gov
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
4 recommended
📰
Source
cisa.gov

Path Traversal and Sensitive Info Leak in Siemens SIMATIC S7 Webserver API .NET Client Library (CVE‑2026‑85114, CVE‑2026‑85115)

What It Is – The .NET client library for Siemens SIMATIC S7 Webserver API (versions < 3.3.61 and < 3.3.62) contains two high‑severity flaws: a path‑traversal issue that lets an attacker write files outside the intended download directory, and an error‑message disclosure that reveals sensitive information.

Exploitability – Both vulnerabilities have a CVSS v3 base score of 7.5 (High). No public exploit code is known, but the flaws are trivial to trigger by manipulating the ticket response from a compromised server.

Affected Products – Siemens SIMATIC S7 Webserver API .NET Client Library (all releases prior to 3.3.61/3.3.62).

Why It Matters for Trust & Control Assurance

  • Demonstrates the need for continuous monitoring of third‑party component versions against secure‑configuration controls.
  • Highlights gaps in file‑system access controls that must be evidenced for audit readiness across multiple frameworks.
  • Provides a concrete example of why a defensible evidence trail (patch status, version inventory) is a prerequisite for enterprise‑level trust.

Recommended Actions

  1. Upgrade immediately to the Siemens‑released version ≥ 3.3.62.
  2. Validate all inbound filenames against a whitelist and enforce strict path canonicalization.
  3. Enable file‑integrity monitoring and log any unexpected writes outside the download directory.
  4. Incorporate the library’s version into your continuous component‑risk inventory and map the remediation to the “secure configuration” control objective.

Source: CISA Advisory – ICSA‑26‑295‑10

📰 Original Source
https://www.cisa.gov/news-events/ics-advisories/icsa-26-295-10 ↗

This Verisq Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Vulnerability exposure

Is this CVE in your supply chain?

Verisq matches published vulnerabilities against the software your vendors run, so you know which relationships this touches before the next review.

See vendor exposure →