As reported by CISA in advisory ICSA-26-321-01, Dorsett Controls InfoScan versions 1.45.0 and earlier contain five vulnerabilities that collectively threaten the confidentiality and integrity of industrial control system environments — particularly in water and wastewater utilities, the critical infrastructure sector this product primarily serves.
What makes this advisory notable is not a single headline flaw but the combination of weaknesses. When an attacker can chain improper TLS certificate validation (CVE-2026-117659) with hard-coded cryptographic keys and missing authentication for critical functions, the blast radius extends well beyond a single endpoint. The Electron desktop client's disabled security boundaries — nodeIntegration enabled, contextIsolation disabled, webSecurity disabled — represent a class of misconfiguration that effectively nullifies the sandbox protections modern desktop frameworks are supposed to provide.
Vulnerability Summary
| CVE ID | Weakness Class | CVSS v3.1 | Severity |
|---|---|---|---|
| CVE-2026-117659 | Improper Certificate Validation (CWE-295) | 8.1 | HIGH |
| CVE-2026-120157 | Exposure of Sensitive System Information | — | HIGH |
| CVE-2026-120255 | Use of Hard-coded Cryptographic Key | — | HIGH |
| CVE-2026-120260 | Missing Authentication for Critical Function | — | HIGH |
| CVE-2026-120271 | Generation of Error Message Containing Sensitive Info | — | HIGH |
| CVE-2026-120298 | (Additional affected-product CVE) | — | HIGH |
Affected product: Dorsett Controls InfoScan <=1.45.0
Patch status: Vendor fix available — update to InfoScan v1.46 or higher
Active exploitation: Not confirmed in the wild at time of advisory
Sector impact: Water and Wastewater Systems; deployments worldwide
Why This Matters Beyond Water Utilities
The water and wastewater sector has been under heightened scrutiny since the 2021 Oldsmar incident and subsequent EPA enforcement actions. InfoScan deployments in this sector often sit on OT networks with limited segmentation, meaning credential recovery or MITM capability against a single workstation could provide a foothold into broader SCADA infrastructure.
Hard-coded cryptographic keys are not a configuration oversight — they are a design defect. No amount of network hardening compensates for an attacker who already possesses the decryption key embedded in the binary.
The Electron client misconfigurations are equally concerning. Disabling webSecurity and contextIsolation while enabling nodeIntegration means any content rendered in the client — including content fetched over an untrusted TLS connection — runs with full Node.js privileges. In a post-compromise scenario, this turns a certificate validation bypass into potential remote code execution on the operator workstation.
Who Is Most Exposed
- Water and wastewater facilities running InfoScan <=1.45.0 on operator workstations with network connectivity to SCADA controllers
- Deployments where InfoScan clients communicate across untrusted or flat networks without additional TLS inspection
- Offline/air-gapped installations that may delay patching due to manual update workflows
- Any environment where InfoScan credentials are reused across other plant systems
Shield53 Recommendations
Immediate Actions
Longer-Term Hardening
- Implement network segmentation between InfoScan workstations and SCADA control networks per IEC 62443 zone/conduit architecture.
- Adopt a regular ICS patch management cadence — vendor updates for OT software are infrequent but critical; establish a 30-day SLA for applying HIGH-severity ICS patches.
- Review all Electron-based OT client applications in your environment for the same misconfiguration pattern (nodeIntegration, contextIsolation, webSecurity). This is a systemic problem, not unique to Dorsett.
The broader lesson for asset owners: certificate validation and authentication failures in ICS clients are not theoretical risks. In water and wastewater environments, the gap between a compromised operator workstation and physical process disruption is often a single network hop. Treat this advisory as an urgent patching priority, not a routine update.