Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Network-reachable WebSocket, low complexity, requires a low-privileged Control UI client session (PR:L), no user interaction, full C/I/A impact on the OpenClaw instance with no scope change.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
OpenClaw before 2026.5.18 accepts WebSocket client-declared operator scopes before binding to server-approved pairing or trusted-proxy authorization baseline. Unpaired or restricted trusted-proxy Control UI clients can obtain cached operator.admin authority on live WebSocket connections to execute admin-gated Gateway RPCs.
AnalysisAI
Privilege escalation in OpenClaw before 2026.5.18 allows WebSocket-connected Control UI clients to claim operator.admin scope without server-side validation against pairing or trusted-proxy authorization state. Attackers with low-privileged WebSocket access can invoke admin-gated Gateway RPCs, and no public exploit identified at time of analysis despite CVSS 4.0 score of 8.7.
Technical ContextAI
OpenClaw exposes a Gateway with admin-gated RPCs reached over WebSocket by Control UI clients. The flaw is a CWE-862 Missing Authorization: the server accepts operator-scope claims declared by the client during the WebSocket session and caches them as authority, instead of cross-checking each request against the server-approved pairing record and the trusted-proxy authorization baseline. Per the CPE 'cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*', all OpenClaw application versions prior to 2026.5.18 are affected. Because authorization state is bound to the live WebSocket connection rather than re-derived from server-side trust, an unpaired or restricted client retains elevated 'operator.admin' authority for the lifetime of the socket.
RemediationAI
Vendor-released patch: upgrade OpenClaw to 2026.5.18 or later as described in GHSA-qjpc-qf9m-xwmr (https://github.com/openclaw/openclaw/security/advisories/GHSA-qjpc-qf9m-xwmr) and the VulnCheck write-up at https://www.vulncheck.com/advisories/openclaw-scope-elevation-in-trusted-proxy-control-ui-websocket. If immediate patching is not possible, restrict network exposure of the Control UI WebSocket endpoint to trusted management networks or a VPN (trade-off: blocks legitimate remote operators), and require pairing and trusted-proxy enrollment before any WebSocket session is accepted by terminating connections from unpaired clients at the reverse proxy (trade-off: may break provisioning workflows that rely on first-connect pairing). As an additional compensating control, disable or block admin-gated Gateway RPC routes for clients whose pairing or trusted-proxy state is not server-confirmed, accepting that this reduces functionality for legitimately restricted operators until upgrade.
Auth bypass in OpenClaw voice-call extension before 2026.2.1. EPSS 0.68%. PoC and patch available.
Privilege escalation in OpenClaw (pre-2026.3.28) allows unauthenticated remote attackers to gain administrative access b
OpenClaw versions 2026.2.22 through 2026.2.24 contain a privilege escalation vulnerability that allows authenticated att
An authorization mismatch vulnerability in OpenClaw versions prior to 2026.3.1 allows authenticated users with operator.
OpenClaw versions prior to 2026.1.29 automatically establish WebSocket connections to attacker-controlled gateway URLs e
Path traversal in OpenClaw through version 2026.3.23 enables unauthenticated remote attackers to read arbitrary files in
OpenClaw sandbox browser functionality launches x11vnc for noVNC observer sessions without requiring authentication, all
OpenClaw versions before 2026.2.26 allow authenticated attackers to write arbitrary files outside the workspace director
OpenClaw versions prior to 2026.2.22 contain a shell environment variable injection vulnerability in the system.run func
OpenClaw versions prior to 2026.2.22 contain a resource exhaustion vulnerability where the application fails to consiste
OpenClaw versions prior to 2026.3.1 contain a sandbox escape vulnerability that allows authenticated attackers with low
OpenClaw versions 2026.1.30 and below fail to validate Telegram webhook secret tokens when `channels.telegram.webhookSec
Same weakness CWE-862 – Missing Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-36609
GHSA-vcg8-6gf2-cg9j