Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
5.9
OpenClaw: Leaked Credentials Allow Privileged Access Over Plain HTTP
GHSA-3cvx-236h-m9fj
Summary
If you're using OpenClaw and have it set up to allow insecure authentication over plain HTTP, an attacker who gets your credentials could gain high-level access to Control UI. This is a serious risk if you're exposing your credentials or if they've been previously leaked. Update to the latest version of OpenClaw to fix this issue.
What to do
- Update openclaw to version 2026.2.21.
Affected software
| Vendor | Product | Affected versions | Fix available |
|---|---|---|---|
| – | openclaw | <= 2026.2.19-2 | 2026.2.21 |
Original title
OpenClaw has an opt-in insecure Control UI auth over plaintext HTTP could allow privileged access
Original description
## 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.
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.
ghsa CVSS4.0
5.9
Vulnerability type
CWE-285
Improper Authorization
CWE-319
Cleartext Transmission of Sensitive Information
Published: 3 Mar 2026 · Updated: 7 Mar 2026 · First seen: 6 Mar 2026