CVE-2026-32034 — OpenClaw < 2026.2.21 - Insecure Control UI Authentication over Plaintext HTTP

Affected: OpenClaw

OpenClaw versions prior to 2026.2.21 contain an authentication bypass vulnerability in the Control UI when allowInsecureAuth is explicitly enabled and the gateway is exposed over plaintext HTTP, allowing attackers to bypass device identity and pairing verification. An attacker with leaked or intercepted credentials can obtain high-privilege Control UI access by exploiting the lack of secure authentication enforcement over unencrypted HTTP connections.

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

Affected: npm: openclaw

## 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](https://github.com/openclaw/openclaw/pull/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.

Most recent entries from all

CVE-2026-32034 — OpenClaw < 2026.2.21 - Insecure Control UI Authentication over Plaintext HTTP

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