Listen to this Post
The vulnerability is a trusted-proxy Control UI pairing bypass in OpenClaw (npm) versions up to 2026.2.24. When trusted-proxy authentication is enabled, the system accepts a WebSocket connection with `client.id=control-ui` without performing any device identity checks. Crucially, this bypass does not require the connection to have an “operator” role; a session authenticated with only a “node” role can connect using this method. This allows a node-scoped WebSocket client to skip the standard device pairing process entirely. By successfully connecting as an unpaired control interface, the attacker can then reach and execute node event methods that should be restricted. The vulnerability stems from insufficient validation of the client’s role and identity when the `client.id` is set to a trusted value. The fix implemented in commit `ec45c317f5d0631a3d333b236da58c4749ede2a3` adds an additional requirement that the connection must have `role === “operator”` to use this trusted-proxy flow, effectively closing the authorization boundary bypass.
Platform: OpenClaw (npm)
Version: <= 2026.2.24
Vulnerability : UI pairing bypass
Severity: Critical
date: March 3, 2026
Prediction: Patch released 2026.2.25
What Undercode Say:
Analytics
This vulnerability allows an authenticated node-role session to bypass pairing . It exploits trusted-proxy logic by using client.id=control-ui. The attack requires a valid node session. Impact is unauthorized access to node event methods.
Bash Commands & Checks
Check your current OpenClaw version openclaw --version Or if using npm list npm list openclaw Verify if you are running a vulnerable version (<= 2026.2.24) npm list openclaw | grep -E "openclaw@(2026.2.2[0-4]|2026.2.[0-1][0-9]|2026.1.)" Check if the fix commit is present in your local repository (if you installed from source) git log --oneline | grep ec45c317f5d0631a3d333b236da58c4749ede2a3 Upgrade to the patched version (2026.2.25) npm update openclaw@latest Or install the specific patched version npm install [email protected] After upgrading, verify the version again openclaw --version
Exploit:
An authenticated attacker with a node-role session crafts a WebSocket connection request to the trusted-proxy endpoint. The request sets `client.id=control-ui` in the connection parameters. The vulnerable server accepts this connection without requiring device pairing or checking if the session has the operator role. Once connected, the attacker can invoke node event methods that should only be accessible from a properly paired Control UI.
Protection from this CVE
Upgrade to OpenClaw version 2026.2.25 or later immediately . This version introduces the fix requiring `role === “operator”` for the trusted-proxy flow. If immediate upgrade is not possible, consider disabling trusted-proxy authentication temporarily as a workaround. Monitor logs for WebSocket connections with `client.id=control-ui` originating from unexpected node-role sessions.
Impact
Successful exploitation allows an authenticated node-role attacker to bypass pairing and gain unauthorized access to node event execution flows . This represents an authorization boundary bypass, potentially allowing the attacker to perform actions or access data restricted to the control interface, leading to privilege escalation and compromise of the OpenClaw instance.
References
- Fix Commit: ec45c317f5d0631a3d333b236da58c4749ede2a3
🎯Let’s Practice Exploiting & Learn Patching For Free:
Sources:
Reported By: github.com
Extra Source Hub:
Undercode
🔐JOIN OUR CYBER WORLD [ CVE News • HackMonitor • UndercodeNews ]
📢 Follow DailyCVE & Stay Tuned:
𝕏 formerly Twitter 🐦 | @ Threads | 🔗 Linkedin
Geth ECIES Cryptography Flaw Allows Node Key Extraction – CVE-2026-22862 (High)