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).
openclaw (npm)<= 2026.2.19-22026.2.21In these explicitly insecure deployments, an attacker with leaked/intercepted credentials could obtain high-privilege Control UI access.
40a292619e1f2be3a3b1db663d7494c9c2dc0abf (merged 2026-02-20)OpenClaw thanks @Vasco0x4 for reporting.
{
"cwe_ids": [
"CWE-285",
"CWE-319",
"CWE-78"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-03T21:49:18Z",
"nvd_published_at": "2026-03-19T22:16:39Z",
"severity": "MODERATE"
}