Haiwell IoT Cloud HMI Gateway

CVE-2026-19188, Haiwell IoT Cloud HMI Gateway: the diagnostic ping in the web interface runs attacker-supplied shell commands as root, unauthenticated (CVSS 10.0)

CISA published ICS advisory ICSA-26-225-02 on 2026-08-13 for CVE-2026-19188, an OS command injection (CWE-78) in the Haiwell IoT Cloud HMI Gateway, a human-machine-interface gateway from a China-headquartered vendor that CISA reports deployed worldwide across the energy, critical manufacturing, and water and wastewater sectors. The advisory places the defect in the gateway's Net Check diagnostic feature, reachable via the /setting endpoint: the cmdPing Socket.io event fails to properly sanitize user-supplied input before passing it to the underlying operating system, so an attacker injects and executes arbitrary OS commands with root privileges (CISA, 2026-08-13). CISA scores it CVSS 3.1 base 10.0 with the vector AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H, network-reachable, low complexity, no privileges, no user interaction, and a scope change reflecting that the injected commands run outside the web application's own boundary.

Two properties in the structured record decide the urgency, and neither is the score. The advisory's SSVC decision data records exploitation as none observed but automatability as yes; CISA's assessment that the steps from reconnaissance through exploitation can be reliably scripted against every reachable instance (CISA, 2026-08-13). A no-credential, no-interaction root primitive that a script can find and fire at scale does not stay unexploited because nobody has tried yet; it stays unexploited until somebody writes the loop. The second is remediation shape: only version 3.40.1.12 appears in the affected list, and Haiwell's fix is patch version Scada-v3.50.1.19, published as a download on the vendor's own site rather than as a firmware push, so applying it is an operator action on each unit (CISA, 2026-08-13). CISA's standing guidance in the same advisory is to minimise network exposure for control-system devices, keep them off the internet, place them behind firewalls isolated from business networks, and use more secure methods such as a VPN where remote access is required.

For a defender the exposure question is sharper than the patch question, because an HMI gateway exists to be reached remotely, that is its product function, and the diagnostic ping is a feature an operator is meant to use. Detection concepts, telemetry class first: in network telemetry at the perimeter and in front of the OT segment, surface any inbound session to the gateway's management interface from outside the expected engineering-access source ranges, and specifically WebSocket or Socket.io connections carrying cmdPing events whose host argument contains shell metacharacters, a semicolon, pipe, backtick or command-substitution syntax where a hostname or address belongs. On the device or in any host telemetry available from it, a root-owned process spawned by the gateway service other than the ping utility it legitimately invokes is the post-exploitation signal, as is an outbound connection initiated by the gateway process shortly after inbound management traffic; an OT gateway that starts calling out immediately after being asked to run a diagnostic is not doing what it was asked.

Triage: the Net Check feature genuinely spawns a ping process when an engineer uses it, so process creation from the gateway service is not by itself the discriminator. What separates the two is the argument and the source: a legitimate diagnostic carries a bare hostname or IP address from an engineering workstation inside the maintenance path, while the exploited call carries shell syntax in the same field and arrives from outside that path, and the resulting process is something other than the ping binary.