CISA Details Siemens S7 Webserver Client File and Password Exposure
Quick Answer
Deploy .NET Client Library 3.3.62 or later and review download destinations and diagnostic access for possible PLC restore-password exposure.
Confirm Scope And Apply The Supported Remediation
What to do now: Identify applications embedding the library, resolved package versions, ticket-download directories, overwrite settings and log destinations. Path traversal requires attacker influence over the remote ticket response. Password disclosure requires access to logs or diagnostics containing the exception. Update the library and redeploy its consumers. Restrict write permissions and diagnostic access while scheduling the fix; investigate any restore-password exposure through the normal credential-response process. Test ticket downloads with controlled invalid filenames and verify that error output redacts restore passwords. Retain dependency, deployment and test evidence without copying secrets into the change record.
Last verified: 2026-11-17 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | .NET Client Library for SIMATIC S7 Webserver API |
|---|---|
| Advisory | ICSA-26-321-02 |
| CVEs | CVE-2026-85114, CVE-2026-85115 |
| Authoritative release date | 2026-11-17T12:00:00Z — CISA release timestamp in the advisory page. |
| Authority revision date | No separate material revision is confirmed for this CISA release. |
| Affected versions | CVE-2026-85114 affects versions before 3.3.61; CVE-2026-85115 affects versions before 3.3.62. |
| Fixed version | .NET Client Library 3.3.62 or later covers both issues; 3.3.61 fixes the path-traversal issue |
| CVSS base score | 7.5 (CVSS v3.1, CVE-2026-85114); 5.5 (CVE-2026-85115) |
| CVSS severity | High |
| Exploitation status | The cited CISA ICS advisory does not confirm exploitation of these products in the wild.; no exploitation claim is inferred. |
What Changed
CISA describes unsafe filenames in ticket downloads and PLC restore passwords included in HTTP error messages. The two issues have different fixed-version boundaries.
What To Validate Now
- Inventory. Identify applications embedding the library, resolved package versions, ticket-download directories, overwrite settings and log destinations.
- Establish applicability. Path traversal requires attacker influence over the remote ticket response. Password disclosure requires access to logs or diagnostics containing the exception.
- Remediate. Update the library and redeploy its consumers. Restrict write permissions and diagnostic access while scheduling the fix; investigate any restore-password exposure through the normal credential-response process.
- Validate. Test ticket downloads with controlled invalid filenames and verify that error output redacts restore passwords. Retain dependency, deployment and test evidence without copying secrets into the change record.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Installing 3.3.61 alone does not cover both disclosures. Updating the client library does not erase credentials already recorded in retained logs.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.

