CVE-2026-32057
High · 7.1CVSS
7.1
EPSS
0.6%
Published
Mar 21, 2026
CISA due date
—
The record
OpenClaw versions prior to 2026.2.25 contain an authentication bypass vulnerability in the trusted-proxy Control UI pairing mechanism that accepts client.id=control-ui without proper device identity verification. An authenticated node role websocket client can exploit this by using the control-ui client identifier to skip pairing requirements and gain unauthorized access to node event execution flows.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| npm | openclaw | 0 | 2026.2.25 |
Related vulnerabilities
- GHSA-vvgp-4c28-m3jm OpenClaw has a Trusted-proxy Control UI pairing bypass which allows unpaired node sessions Same vulnerability
- GHSA-4hpg-mp64-x7xq OpenClaw: Internal/webchat command auth could inherit ownerAllowFrom wildcard state Also affects openclaw
- GHSA-8mg9-j9cf-54cj OpenClaw: Empty-scope device re-pairing could confuse caller scope containment Also affects openclaw
- GHSA-rx78-29qr-5hq8 OpenClaw: Workspace-derived service PATH could influence trash command selection Also affects openclaw
- GHSA-wc84-j36w-pw4x OpenClaw: Workspace .env STATE_DIRECTORY could influence bundled runtime dependency roots Also affects openclaw
- GHSA-cw4q-gqg5-g38h OpenClaw: Discord allowFrom could bind to mutable display names Also affects openclaw
- GHSA-mpc8-jxjh-qpgh OpenClaw: Focus command could miss controlScope enforcement Also affects openclaw
- GHSA-24vr-rprv-67rf OpenClaw: Workspace .env npm_execpath could influence bundled runtime dependency install Also affects openclaw