CVE-2026-32057: 
OpenClaw (formerly Moltbot or Clawdbot) vulnerability analysis and mitigation

CVE-2026-32057 is an authentication bypass vulnerability in OpenClaw's trusted-proxy Control UI pairing mechanism affecting all versions prior to 2026.2.25 (npm package). The flaw allows an authenticated node role WebSocket client to spoof the client.id=control-ui identifier and skip device identity verification, gaining unauthorized access to node event execution flows. It was published on March 21, 2026, and assigned a CVSS v3.1 base score of 7.1 (High) and a CVSS v4.0 base score of 6.0 (Medium) (GitHub Advisory, VulnCheck).

The root cause is classified as CWE-807 (Reliance on Untrusted Inputs in a Security Decision): the gateway's WebSocket message handler accepted client.id=control-ui as sufficient to trigger the trusted-proxy Control UI authentication path without also verifying that the connecting session held the operator role or a valid device identity. Specifically, the trustedProxyAuthOk check in src/gateway/server/ws-connection/message-handler.ts was missing a role === "operator" condition, meaning a node-scoped session could satisfy the check by simply presenting the control-ui client identifier. The fix adds the missing role assertion at two locations in the handler, and new tests confirm that node-role connections with the control-ui identifier are now rejected with a CONTROL_UI_DEVICE_IDENTITY_REQUIRED error code (GitHub Commit, GitHub Advisory).

A successful exploit allows an authenticated attacker with only node role WebSocket access to cross an authorization boundary into node event execution flows normally reserved for operator-role Control UI sessions. The primary impact is high integrity — the attacker can invoke node event methods without proper pairing or operator authorization. A secondary low confidentiality impact exists through potential information disclosure via those event flows; availability is not affected (GitHub Advisory, VulnCheck).

No public proof-of-concept exploit code is known to exist, and there is no evidence of in-the-wild exploitation at this time. The EPSS score is approximately 0.052% (0.000520), indicating a low probability of near-term exploitation. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. Exploitation requires an existing authenticated node role WebSocket session, which limits the attacker pool but does not require operator privileges (GitHub Advisory, VulnCheck).

1. Obtain node role credentials: Acquire valid credentials sufficient to authenticate as a node role WebSocket client against a target OpenClaw instance running a version ≤ 2026.2.24 with trusted-proxy authentication enabled.
2. Establish WebSocket connection: Open a WebSocket connection to the OpenClaw gateway endpoint, supplying required trusted-proxy headers (e.g., x-forwarded-user, x-forwarded-proto) as expected by the proxy configuration.
3. Spoof the control-ui client identifier: In the connect request payload, set client.id to control-ui (matching GATEWAY_CLIENT_NAMES.CONTROL_UI) while authenticating with a node role session and omitting or providing no valid device identity.
4. Bypass pairing check: Because the pre-patch trustedProxyAuthOk condition only checked isControlUi, resolvedAuth.mode === "trusted-proxy", authOk, and authMethod === "trusted-proxy" — without verifying role === "operator" — the gateway accepts the connection as if it were a legitimate Control UI session.
5. Access node event execution flows: Invoke node event methods (RPC calls) that are normally restricted to paired operator-role Control UI sessions, enabling unauthorized command execution within those flows (GitHub Advisory, GitHub Commit).

• Network: WebSocket connect requests to the OpenClaw gateway where client.id is set to control-ui originating from a node-role session; connections lacking a valid device identity signature but presenting trusted-proxy headers.
• Logs: Gateway logs showing a node-role session successfully completing the trustedProxyAuthOk path without a paired device identity (pre-patch); absence of CONTROL_UI_DEVICE_IDENTITY_REQUIRED or PAIRING_REQUIRED error codes for control-ui connections from node-role clients.
• Application Behavior: Node event execution flow methods being invoked from sessions that have not completed the standard Control UI pairing process; unexpected RPC calls to node event methods from sessions authenticated only at the node role level.

Upgrade OpenClaw (npm) to version 2026.2.25 or later, which adds the role === "operator" check to the trustedProxyAuthOk condition in the gateway WebSocket message handler (GitHub Commit, GitHub Advisory). As interim mitigations prior to patching: implement network segmentation to restrict WebSocket connections to trusted node sources only; monitor gateway logs for node-role sessions presenting client.id=control-ui; and consider disabling trusted-proxy authentication mode if not strictly required (VulnCheck).

The vulnerability was reported by researcher tdjackey and acknowledged in the GitHub Security Advisory published by steipete on February 26, 2026. The advisory was assigned a "Moderate" severity rating by the OpenClaw maintainers. No significant broader media coverage or notable external researcher commentary has been identified beyond the advisory and standard CVE aggregator coverage (GitHub Advisory).