Back to Intelligence

CVE-2026-85114 & CVE-2026-85115: Siemens SIMATIC S7 Webserver API Client Path Traversal — Detection and Remediation Guide

SA
Security Arsenal Team
November 17, 2026
12 min read

CISA has published ICS Advisory ICSA-26-321-02 covering two vulnerabilities in Siemens' .NET Client Library for SIMATIC S7 Webserver API. The library is a software development component used to build Windows-based applications that communicate with SIMATIC S7 PLC web servers — commonly found in engineering workstations, HMI integrations, custom diagnostics tools, and OT automation scripts.

The vulnerabilities carry a CVSS v3.1 score of 7.5 (HIGH) and expose a classic but dangerous OT risk: path traversal (CWE-22) and information disclosure via error messages (CWE-209). Because this is a client library, the flaw is triggered when a vulnerable application connects to a malicious or compromised server endpoint — or when an attacker can intercept and manipulate server responses. In practical terms: a rogue or compromised S7 PLC, or an attacker performing a man-in-the-middle attack on OT network segments, can exploit the client-side parsing logic to write arbitrary files outside the intended download directory or extract sensitive information from error responses.

For organizations running Siemens S7-1200/S7-1500 environments with custom .NET integrations, this advisory demands immediate attention. Engineering workstations and OT-adjacent Windows systems are high-value targets for ransomware operators and nation-state actors alike — a path traversal primitive that enables arbitrary file write on these systems can be leveraged for code execution, credential theft, or lateral movement into the ICS environment.


Technical Analysis

Affected Products

ProductAffected VersionsFixed Version
.NET Client Library for SIMATIC S7 Webserver API< 3.3.61 (3.3.x branch)3.3.61
.NET Client Library for SIMATIC S7 Webserver API< 3.3.62 (3.3.x branch)3.3.62

The library is distributed as a NuGet package and standalone DLL for .NET Framework and .NET Core/5+ applications. Any custom application, script, or service that references this library is potentially vulnerable.

CVE Breakdown

CVE-2026-85114 — Improper Limitation of a Pathname to a Restricted Directory (Path Traversal, CWE-22)

The client library fails to properly sanitize file paths returned by the S7 webserver during file download operations. When the application requests a file from the PLC's webserver (e.g., diagnostic logs, recipe files, firmware backups), the server response includes a target path. The vulnerable library does not adequately validate that this path stays within the configured download directory, allowing directory traversal sequences (../..\..\) to redirect the write operation to arbitrary locations on the client filesystem.

From a defender's perspective, this is the more dangerous of the two flaws. In an OT context, exploitation scenarios include:

  • A compromised or spoofed S7 PLC returns a malicious path, causing the client application to overwrite critical files (e.g., .exe, .dll, .config, PowerShell profiles, scheduled task definitions) on the engineering workstation.
  • An attacker with MITM position on the OT network segment (unencrypted HTTP or weak TLS on the S7 webserver) intercepts a legitimate file download and injects a traversal path.
  • The arbitrary file write can be chained to achieve remote code execution by dropping a malicious DLL into an application directory (DLL hijacking) or overwriting an executable.

CVE-2026-85115 — Generation of Error Message Containing Sensitive Information (CWE-209)

The library generates verbose error messages that may expose sensitive information — including internal file paths, configuration details, connection strings, or authentication tokens — when operations fail. In a client-server model, these error details could be logged, displayed to operators, or captured by an attacker who can trigger error conditions. While less immediately exploitable than the path traversal, this information disclosure aids reconnaissance and attack chain development.

Attack Chain Summary

  1. Attacker gains control of an S7 PLC webserver endpoint (via credential compromise, default passwords, or an upstream PLC vulnerability) or establishes MITM on the OT network.
  2. A Windows application using the vulnerable .NET client library initiates a connection to the malicious/compromised server.
  3. During a file download operation, the server responds with a crafted path containing directory traversal sequences.
  4. The vulnerable library writes the file content to the attacker-controlled path outside the intended download directory.
  5. Simultaneously, triggered error responses leak sensitive configuration and path information.

Exploitation Status

As of the advisory publication date, there is no confirmed in-the-wild exploitation and no public proof-of-concept code. The vulnerabilities are not currently listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. However, given the CVSS 7.5 severity, the simplicity of path traversal exploitation, and the high-value nature of engineering workstations in OT environments, organizations should treat this as a priority remediation item.


Detection & Response

The primary detection surface for this vulnerability is the Windows endpoint running applications built with the vulnerable library. Network-level detection focuses on identifying anomalous file write patterns and suspicious server responses.

SIGMA Rules

YAML
---
title: Suspicious File Write Outside Download Directory by .NET Application
id: 7a3f1c82-9e4b-4d67-bc12-3e5a8f901234
status: experimental
description: Detects .NET applications writing files to sensitive system directories that may indicate exploitation of path traversal in Siemens SIMATIC S7 Webserver API client library (CVE-2026-85114).
references:
  - https://www.cisa.gov/news-events/ics-advisories/icsa-26-321-02
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.initial_access
  - attack.t1190
logsource:
  category: file_event
  product: windows
detection:
  selection_img:
    Image|contains:
      - '\dotnet\'
      - '\AppData\'
      - '\Program Files\'
      - '\Program Files (x86)\'
  selection_target:
    TargetFilename|contains:
      - '\Windows\System32\'
      - '\Windows\SysWOW64\'
      - '\Program Files\'
      - '\Program Files (x86)\'
      - '\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\'
      - '\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\'
  filter_legitimate:
    Image|endswith:
      - '\setup.exe'
      - '\msiexec.exe'
      - '\installer.exe'
  condition: selection_img and selection_target and not filter_legitimate
falsepositives:
  - Legitimate software installers and updaters
  - Development tools writing to system directories
level: high
---
title: Path Traversal Pattern in HTTP Response from OT Network Segment
id: 550d9a23-0f72-4e3a-a8c5-1d2f3b4c5d6e
status: experimental
description: Detects HTTP responses containing directory traversal sequences originating from OT/ICS network segments, potentially indicating exploitation of CVE-2026-85114 against Siemens S7 Webserver API clients.
references:
  - https://www.cisa.gov/news-events/ics-advisories/icsa-26-321-02
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.initial_access
  - attack.t1190
logsource:
  category: proxy
  product: zeek
detection:
  selection:
    resp_mime_types:
      - 'application/octet-stream'
      - 'text/plain'
      - 'application/json'
    uri|contains:
      - '../'
      - '..\\'
      - '%2e%2e%2f'
      - '%2e%2e%5c'
      - '..%2f'
      - '..%5c'
  condition: selection
falsepositives:
  - Legitimate file transfer operations with relative paths
  - Web application testing tools
level: medium

KQL (Microsoft Sentinel / Defender)

KQL — Microsoft Sentinel / Defender
// Hunt for file writes to sensitive directories by processes that may be using the vulnerable Siemens library
DeviceFileEvents
| where TimeGenerated > ago(7d)
| where FolderPath has_any ("\\Windows\\System32\\", "\\Windows\\SysWOW64\\", "\\Startup\\", "\\Program Files\\")
| where InitiatingProcessFileName has_any ("dotnet", "simatic", "s7", "siemens")
    or InitiatingProcessCommandLine has_any ("simatic", "s7webserver", "siemens")
| project TimeGenerated, DeviceName, InitiatingProcessFileName, InitiatingProcessCommandLine, FolderPath, FileName, SHA256
| order by TimeGenerated desc;

// Hunt for network connections from engineering workstations to S7 PLC webserver ports with anomalous patterns
DeviceNetworkEvents
| where TimeGenerated > ago(7d)
| where RemotePort in (80, 443, 8080, 8443)
| where InitiatingProcessFileName has_any ("dotnet", "simatic", "s7")
    or InitiatingProcessCommandLine has_any ("simatic", "s7webserver")
| summarize ConnectionCount = count(), UniqueRemoteIPs = dcount(RemoteIP) by DeviceName, InitiatingProcessFileName, bin(TimeGenerated, 1h)
| where ConnectionCount > 50 or UniqueRemoteIPs > 10
| order by ConnectionCount desc;

// Hunt for error events indicating potential information disclosure via verbose error messages
SecurityEvent
| where TimeGenerated > ago(7d)
| where EventID in (4688, 4689)
| where CommandLine has_any ("path", "directory", "unauthorized", "access denied")
| where Process has_any ("dotnet", "simatic")
| project TimeGenerated, Computer, Process, CommandLine, ParentProcessName
| order by TimeGenerated desc

Velociraptor VQL

VQL — Velociraptor
-- Hunt for arbitrary file writes by .NET applications to sensitive system directories
SELECT 
    Pid,
    Name,
    CommandLine,
    Exe,
    Username,
    CreateTime
FROM pslist()
WHERE CommandLine =~ '(?i)(simatic|s7webserver|siemens)'
   OR Exe =~ '(?i)(dotnet|simatic)'

-- Identify recently modified files in sensitive directories by non-system processes
SELECT 
    FullPath,
    Size,
    Mtime,
    Atime
FROM glob(globs='C:\\Windows\\System32\\**')
WHERE Mtime > now() - 604800
ORDER BY Mtime DESC

-- Check for established network connections from .NET processes to OT segments
SELECT 
    Pid,
    Name,
    LocalIP,
    LocalPort,
    RemoteIP,
    RemotePort,
    Status
FROM netstat()
WHERE Name =~ '(?i)(dotnet|simatic)'
  AND RemoteIP =~ '^(10\\.|172\\.(1[6-9]|2[0-9]|3[01])\\.|192\\.168\\.)'
  AND RemotePort in (80, 443, 8080, 8443)

Remediation Script

PowerShell
<#
.SYNOPSIS
    Detection and remediation script for CVE-2026-85114 / CVE-2026-85115
    Siemens .NET Client Library for SIMATIC S7 Webserver API path traversal.
.DESCRIPTION
    Scans for vulnerable library versions, checks for indicators of exploitation,
    and provides remediation guidance. Run with administrative privileges.
.NOTES
    Author: Security Arsenal
    Date: 2026-04-06
    Reference: https://www.cisa.gov/news-events/ics-advisories/icsa-26-321-02
#>

param(
    [switch]$Remediate = $false,
    [switch]$ScanOnly = $true
)

$VulnerableVersions = @('3.3.61', '3.3.62')
$LibraryNames = @('Siemens.Simatic.S7.Webserver.API', 'S7WebserverAPI', 'Simatic.S7')
$SuspiciousPaths = @(
    "$env:SystemRoot\System32",
    "$env:SystemRoot\SysWOW64",
    "$env:ProgramData\Microsoft\Windows\Start Menu\Programs\Startup",
    "$env:APPDATA\Microsoft\Windows\Start Menu\Programs\Startup"
)

Write-Host "[+] Siemens SIMATIC S7 Webserver API Vulnerability Scanner" -ForegroundColor Cyan
Write-Host "[+] Reference: CISA ICSA-26-321-02 | CVE-2026-85114, CVE-2026-85115`n" -ForegroundColor Cyan

# Check for vulnerable NuGet packages in common locations
Write-Host "[*] Scanning for vulnerable library installations..." -ForegroundColor Yellow
$NuGetPaths = @(
    "$env:USERPROFILE\.nuget\packages",
    "$env:ProgramFiles\dotnet\shared",
    "$env:ProgramFiles(x86)\dotnet\shared"
)

foreach ($path in $NuGetPaths) {
    if (Test-Path $path) {
        $packages = Get-ChildItem -Path $path -Recurse -Filter "*.nuspec" -ErrorAction SilentlyContinue |
            Where-Object { $_.Name -match '(?i)(simatic|s7|siemens)' }
        foreach ($pkg in $packages) {
            $version = ($pkg.DirectoryName -split '\\')[-1]
            Write-Host "[!] Found: $($pkg.FullName)" -ForegroundColor Red
            Write-Host "    Version: $version" -ForegroundColor Red
            if ($version -lt '3.3.61') {
                Write-Host "    STATUS: VULNERABLE - Update to 3.3.61 or later`n" -ForegroundColor Red
            }
        }
    }
}

# Check for recently modified files in sensitive directories
Write-Host "[*] Checking for suspicious file modifications in system directories..." -ForegroundColor Yellow
$RecentFiles = foreach ($sp in $SuspiciousPaths) {
    Get-ChildItem -Path $sp -File -ErrorAction SilentlyContinue |
        Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(-7) } |
        Select-Object FullName, LastWriteTime, Length
}

if ($RecentFiles) {
    Write-Host "[!] Recently modified files in sensitive directories (last 7 days):" -ForegroundColor Yellow
    $RecentFiles | Format-Table -AutoSize
} else {
    Write-Host "[+] No suspicious recent modifications detected.`n" -ForegroundColor Green
}

# Check for .NET processes with network connections to OT segments
Write-Host "[*] Checking for .NET processes with OT network connections..." -ForegroundColor Yellow
$OTNetworks = @('10.', '172.16.', '172.17.', '172.18.', '172.19.', '172.2', '172.30.', '172.31.', '192.168.')
$DotNetConnections = Get-NetTCPConnection -State Established -ErrorAction SilentlyContinue |
    Where-Object {
        $proc = Get-Process -Id $_.OwningProcess -ErrorAction SilentlyContinue
        $proc.Name -match '(?i)(dotnet|simatic|s7)'
        foreach ($net in $OTNetworks) { if ($_.RemoteAddress -like "$net*") { $true } }
    } |
    Select-Object @{N='Process';E={(Get-Process -Id $_.OwningProcess).Name}},
                  LocalAddress, LocalPort, RemoteAddress, RemotePort, State

if ($DotNetConnections) {
    Write-Host "[!] Active .NET connections to potential OT networks:" -ForegroundColor Yellow
    $DotNetConnections | Format-Table -AutoSize
} else {
    Write-Host "[+] No suspicious OT network connections detected.`n" -ForegroundColor Green
}

# Remediation guidance
Write-Host "`n[=== REMEDIATION GUIDANCE ===]" -ForegroundColor Cyan
Write-Host @"
1. IMMEDIATE ACTION: Update all applications using the Siemens .NET Client Library
   - Target version: 3.3.61 or later (3.3.x branch)
   - Download: https://support.industry.siemens.com/cs/document/109814500/

2. INVENTORY: Identify all applications using this library
   - Search for: Siemens.Simatic.S7.Webserver.API.dll
   - Check NuGet package references in .csproj files
   - Review deployed applications in OT environments

3. NETWORK SEGMENTATION: Isolate S7 PLC webserver interfaces
   - Ensure S7 webserver ports (80/443/8080) are only accessible from authorized engineering workstations
   - Implement firewall rules blocking unsolicited PLC-to-client connections

4. MONITORING: Deploy detection rules for path traversal attempts
   - Monitor file writes outside designated download directories
   - Alert on directory traversal patterns in HTTP traffic to/from OT segments

5. HARDENING: Apply defense-in-depth measures
   - Enable TLS on all S7 webserver connections
   - Use certificate pinning to prevent MITM attacks
   - Run engineering workstation applications with least privilege

For questions or assistance, contact Security Arsenal at securityarsenal.com
"@ -ForegroundColor White

Remediation

Immediate Actions

  1. Identify affected installations. Scan all Windows engineering workstations, HMI systems, and OT-adjacent servers for applications using the vulnerable .NET Client Library. Check NuGet package caches, application directories, and software inventories.

  2. Update to the latest version. Siemens has released fixed versions. Update all applications to use:

    • 3.3.61 or later (for 3.3.x branch)
    • 3.3.62 or later (for 3.3.x branch)

    Download the updated library from the Siemens Industry Online Support portal.

  3. Rebuild and redeploy affected applications. Simply updating the NuGet package reference is not sufficient — applications must be rebuilt and redeployed to ensure the vulnerable DLL is replaced.

Network-Level Mitigations

  • Segment OT networks. Ensure S7 PLC webserver interfaces (ports 80, 443, 8080) are only accessible from authorized engineering workstations via firewall rules or data diodes.
  • Enforce TLS. Configure S7 webservers to require HTTPS with valid certificates. Implement certificate pinning in client applications to prevent man-in-the-middle attacks.
  • Block unsolicited server-initiated connections. The exploitation model requires a client connecting to a malicious server — restricting which endpoints can initiate connections reduces attack surface.

Application Hardening

  • Validate all file paths. If you maintain custom applications using this library, implement additional server response validation. Reject any file paths containing .. sequences or absolute paths.
  • Run with least privilege. Engineering workstation applications should not run with administrative or SYSTEM privileges, limiting the impact of arbitrary file writes.
  • Implement download directory sandboxing. Use application-level controls to restrict write operations to a single designated directory.

Monitoring & Detection

  • Deploy the Sigma, KQL, and VQL rules provided above to detect exploitation attempts.
  • Monitor for file writes to C:\Windows\System32, C:\Windows\SysWOW64, and Startup folders by .NET processes.
  • Alert on HTTP responses from OT network segments containing directory traversal patterns (../, ..\, URL-encoded equivalents).

Official References


Executive Takeaways

ActionPriorityTimeline
Inventory all applications using the vulnerable libraryCritical24-48 hours
Update to version 3.3.61/3.3.62 and redeployCritical7 days
Segment S7 PLC webserver network interfacesHigh14 days
Deploy detection rules for path traversal attemptsHigh7 days
Enforce TLS on all S7 webserver connectionsMedium30 days

This advisory underscores a persistent challenge in OT security: client-side vulnerabilities in libraries used to communicate with industrial controllers. The "server is trusted" assumption that pervades ICS environments creates opportunities for attackers who compromise PLCs or intercept network traffic. Defense-in-depth — including network segmentation, TLS enforcement, least privilege, and robust endpoint monitoring — remains essential.

For organizations operating Siemens S7 environments, treat this as a priority patch cycle. The combination of arbitrary file write and information disclosure on engineering workstations presents a clear path to deeper OT network compromise.

Related Resources

Security Arsenal Managed SOC Services AlertMonitor Platform Book a SOC Assessment soc-mdr Intel Hub

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.