Path Traversal in NET Client Library for SIMATIC S7 Webserver API (CVE-2026-85114)
Summary
Path traversal in NET Client Library for SIMATIC S7 Webserver API (CVE-2026-85114). Data can be tampered with by attackers.
Original description
The description as published by the source.
A vulnerability has been identified in .NET Client Library for SIMATIC S7 Webserver API (All versions < V3.3.61). Affected applications do not properly validate filenames received from remote servers during ticket downloads.
This could allow an attacker who can manipulate the ticket response to write arbitrary files outside the intended download directory and, when overwriting is enabled, replace existing files accessible to the application.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-85114 has been found in NET Client Library for SIMATIC S7 Webserver API.
Data can be tampered with by attackers. CVSS score: 7.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "NET Client Library for SIMATIC S7 Webserver API CVE-2026-85114" on the vendor's site.
CVE-2026-85114 (NET Client Library for SIMATIC S7 Webserver API) — CWE-22 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in NET Client Library for SIMATIC S7 Webserver API.
Check the vendor advisory for the affected versions of NET Client Library for SIMATIC S7 Webserver API.
Severity: High (CVSS 7.5/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで NET Client Library for SIMATIC S7 Webserver API を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。