CVE-2026-32057
OpenClaw has a Trusted-proxy Control UI pairing bypass which allows unpaired node sessions
Description
## Summary A trusted-proxy Control UI pairing bypass accepted `client.id=control-ui` without device identity checks. The bypass did not require `operator` role, so an authenticated `node` role session could connect unpaired and reach node event methods. ## Impact With trusted-proxy authentication enabled, a `node` role websocket client could skip pairing by using `client.id=control-ui`. That created an authorization boundary bypass from a node-scoped connection into node event execution flows. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected range: `<= 2026.2.24` - Latest published vulnerable version: `2026.2.24` - Patched in next release: `2026.2.25` (pre-set below so this advisory is ready to publish after npm release) ## Fix The trusted-proxy Control UI bypass now additionally requires `role === "operator"`. ### Fix Commit(s) - `ec45c317f5d0631a3d333b236da58c4749ede2a3` ## Release Process Note `patched_versions` is intentionally pre-set to the release (`2026.2.25`). Advisory published with npm release `2026.2.25`.2.25` is published, the remaining GHSA action is to publish this advisory. OpenClaw thanks @tdjackey for reporting.
How to fix CVE-2026-32057
To remediate CVE-2026-32057, upgrade the affected package to a fixed version below.
- —upgrade to 2026.2.25 or later
Is CVE-2026-32057 being exploited?
Low — EPSS is 0.1%, meaning exploitation activity has not been observed at scale.
Affected packages (1)
- from 0, < 2026.2.25