Executive Summary

In November 2026, CISA published ICS Advisory ICSA-26-321-01 disclosing six vulnerabilities in Dorsett Controls InfoScan versions 1.45.0 and earlier, a building and infrastructure management platform deployed globally in water and wastewater critical infrastructure. The flaws—spanning improper TLS certificate validation, hard-coded cryptographic keys, missing authentication on critical endpoints, unauthenticated information disclosure, and verbose error messages leaking Node.js stack traces—collectively enable an attacker to intercept network communications, recover database credentials, enumerate usernames and system configuration without authentication, and map internal infrastructure from the publicly distributed installer. The highest-severity vulnerability (CVE-2026-117659) scores 8.1 CVSS v3.1. Dorsett Controls released InfoScan v1.46 as the remediation.

These vulnerabilities are emblematic of a widening attack surface in operational technology environments where ICS software inherits web-application security debt. With nation-state actors increasingly pre-positioning in water and energy ICS networks, unauthenticated information disclosure and broken TLS validation in internet-facing or VPN-connected OT management clients dramatically lower the bar for initial reconnaissance and credential theft.

Why This Matters Now

Water and wastewater ICS platforms are under heightened nation-state scrutiny following a series of disclosed intrusions against U.S. critical infrastructure. The combination of unauthenticated API endpoints, hard-coded cryptographic keys, and certificate-validation bypass in InfoScan means attackers can silently enumerate targets, steal database credentials, and intercept OT traffic without triggering traditional IT security controls—making rapid patching to v1.46 and network segmentation immediately urgent.

Attack Path Analysis

Related CVEs

MITRE ATT&CK® Techniques

Potential Compliance Exposure

Sector Implications

Sources

Frequently Asked Questions

All versions of InfoScan at or below 1.45.0 are affected. Dorsett Controls recommends updating to v1.46 or higher via the System Maintenance update mechanism or the Dorsett Controls Customer Portal for offline installations.

Cloud Native Security Fabric Mitigations and ControlsCNSF

Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.

Aviatrix Zero Trust CNSF is directly relevant here because the attacker relied on open reachability to unauthenticated endpoints and uncontrolled paths between IT, SCADA, and OT network segments to progress through every stage of this attack. By enforcing identity-aware segmentation and controlled access boundaries, CNSF would likely reduce the attacker's ability to reach internal services, pivot into OT zones, and exfiltrate operational data without detection.

Initial Compromise

Control: Cloud Native Security Fabric (CNSF)

Mitigation: Exposing these endpoints to unauthenticated external traffic represents a reachability problem that CNSF-enforced perimeter segmentation would likely constrain, reducing the attacker's ability to freely probe and enumerate internal service details from outside trusted network boundaries.

Privilege Escalation

Control: Zero Trust Segmentation

Mitigation: Zero Trust segmentation would likely constrain the attacker's ability to reach the MongoDB instance and internal application endpoints directly, reducing the privilege scope achievable even after credential recovery from the binary.

Lateral Movement

Control: East-West Traffic Security

Mitigation: East-west traffic enforcement across the IT/OT boundary would likely constrain the attacker's ability to pivot from the SCADA layer into OT segments, reducing the reachability of BACnet/IP-connected industrial devices even after the Electron client was compromised.

Command & Control

Control: Multicloud Visibility & Control

Mitigation: Multicloud visibility and control over traffic patterns between the Electron client and InfoScan server infrastructure would likely surface anomalous communication paths or unexpected certificate behaviors, reducing the attacker's ability to maintain an undetected man-in-the-middle channel within the ICS environment.

Exfiltration

Control: Egress Security & Policy Enforcement

Mitigation: Egress security policy enforcement would likely constrain outbound data flows from the OT environment to unexpected external destinations, reducing the attacker's ability to move bulk operational and credential data out of the network over uncontrolled channels.

Impact (Mitigations)

If prior CNSF controls had constrained lateral movement into OT segments and limited egress paths, the attacker's operational reach within the water and wastewater environment would likely be significantly reduced, narrowing the set of BACnet/IP devices and control system components reachable for manipulation.

Impact at a Glance

Affected Business Functions

  • Water and Wastewater SCADA/ICS Monitoring and Control
  • Remote Infrastructure Management and Telemetry
  • Operational Technology (OT) Network Security
  • Critical Infrastructure Asset Management
Operational Disruption

Estimated downtime: N/A

Financial Impact

Estimated loss: N/A

Data Exposure

Sensitive system information including customer and internal infrastructure hostnames embedded in publicly distributed installers; MongoDB database credentials recoverable via hard-coded cryptographic keys stored in the Windows registry; usernames and display names of system users; multifactor authentication configuration status; session settings; application and server version information; hardware module firmware versions; BACnet/IP port configurations; internal Node.js filesystem paths, application directory structures, and source file locations disclosed via verbose error messages. No confirmed data exfiltration has been reported; however, chained exploitation of these vulnerabilities in water and wastewater ICS environments could facilitate unauthorized access to operational data, credential compromise, and potential manipulation of water system controls.

Recommended Actions

  • • Apply Zero Trust Segmentation (CNSF) to isolate InfoScan server endpoints and BACnet/IP-accessible OT devices into identity-based microsegment boundaries, enforcing least-privilege access policies that prevent unauthenticated lateral traversal from IT to OT layers and block access to internal API endpoints from untrusted network segments.
  • • Deploy Egress Security & Policy Enforcement (CNSF) with FQDN filtering and outbound traffic controls on all InfoScan server and client hosts to detect and block unauthorized data exfiltration of credentials, configuration data, and OT topology information to attacker-controlled destinations.
  • • Enable Encrypted Traffic Protection (CNSF HPE/MACsec/IPsec) across all InfoScan client-to-server and server-to-database communications to ensure that improper certificate validation vulnerabilities cannot be exploited for man-in-the-middle interception, rendering passive and active traffic interception attacks ineffective even before vendor patching is complete.
  • • Leverage Multicloud Visibility & Control (CNSF) with anomaly detection to baseline normal InfoScan API traffic patterns and generate alerts on unauthenticated or malformed requests to enumeration, version-reporting, and login endpoints — directly detecting CVE-2026-120271 and CVE-2026-120298 exploitation attempts in real time.
  • • Enforce East-West Traffic Security (CNSF) controls between the InfoScan application tier, MongoDB database layer, and OT/BACnet network segments so that even if Electron client boundaries are compromised, workload-to-workload lateral movement is blocked by policy, containing the blast radius of a client-side compromise to the endpoint and preventing OT device enumeration or manipulation.

Secure the Paths Between Cloud Workloads

A cloud-native security fabric that enforces Zero Trust across workload communication—reducing attack paths, compliance risk, and operational complexity.

Cta pattren Image