| Package | Affected versions | Patched versions |
|---|---|---|
| openclaw | < 2026.2.25 | 2026.2.25 |
| openclaw | < 2026.2.25 | 2026.2.25 |
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.
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.
openclaw (npm)<= 2026.2.242026.2.242026.2.25 (pre-set below so this advisory is ready to publish after npm release)The trusted-proxy Control UI bypass now additionally requires role === "operator".
ec45c317f5d0631a3d333b236da58c4749ede2a3patched_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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free