N/A

CVSS Score

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

GHSA-3cvx-236h-m9fj

GHSA-3cvx-236h-m9fj: OpenClaw has an opt-in insecure Control UI auth over plaintext HTTP could allow privileged access

Description

In affected releases, when an operator explicitly enabled gateway.controlUi.allowInsecureAuth: true and exposed the gateway over plaintext HTTP, Control UI authentication could permit privileged operator access without the intended device identity + pairing guarantees.

This required an insecure deployment choice and credential exposure risk (for example, plaintext transit or prior token leak). It was fixed on main in commit 40a292619e1f2be3a3b1db663d7494c9c2dc0abf (PR #20684).

Affected Packages / Versions

Package: openclaw (npm)
Affected published versions: <= 2026.2.19-2
Planned patched version: 2026.2.21

Impact

In these explicitly insecure deployments, an attacker with leaked/intercepted credentials could obtain high-privilege Control UI access.

Fix Commit(s)

40a292619e1f2be3a3b1db663d7494c9c2dc0abf (merged 2026-02-20)

OpenClaw thanks @Vasco0x4 for reporting.

(GitHub Advisory)

Miggo Vulnerability Database

→

GHSA-3cvx-236h-m9fj

GHSA-3cvx-236h-m9fj:

N/A

CVSS Score

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
openclaw	npm	<= 2026.2.19-2	2026.2.21

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability allowed an authentication bypass for the Control UI when gateway.controlUi.allowInsecureAuth was enabled in an insecure deployment over plaintext HTTP. The root cause of this vulnerability is located in the attachGatewayWsMessageHandler function in src/gateway/server/ws-connection/message-handler.ts. This function is responsible for handling WebSocket connections and their authentication.

The analysis of the patch commit 40a292619e1f2be3a3b1db663d7494c9c2dc0abf shows a critical change in this function. Previously, a boolean variable allowControlUiBypass was set to true if gateway.controlUi.allowInsecureAuth was enabled. This bypass flag effectively disabled security checks that enforce a secure context (like HTTPS) and device pairing for the Control UI. The fix removes the influence of allowInsecureAuth on this bypass logic, thereby hardening the authentication process. Now, the bypass is only triggered by a more explicit and dangerously named flag, dangerouslyDisableDeviceAuth.

During an exploitation attempt, a runtime profiler would capture attachGatewayWsMessageHandler in the execution stack, as this function is the entry point for processing the malicious connection request that exploits the authentication bypass. The end-to-end tests modified in the patch further confirm that this function contains the core vulnerable logic.

Vulnerable functions

attachGatewayWsMessageHandler

src/gateway/server/ws-connection/message-handler.ts

The vulnerability lies within the `attachGatewayWsMessageHandler` function, which handles WebSocket connections and authentication. The logic for bypassing security checks for the Control UI was flawed. When `gateway.controlUi.allowInsecureAuth` was set to `true`, the `allowControlUiBypass` variable would become true. This incorrectly bypassed checks for a secure context (HTTPS/localhost) and device identity, allowing an attacker with credentials to gain privileged access over an insecure HTTP connection. The patch corrects this by removing the `allowInsecureControlUi` from the bypass condition, ensuring that `allowInsecureAuth` no longer weakens security.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.