openclaw
Affected
- introduced
0, fixed2026.3.11(semver)
Fixed versions
2026.3.11
Fix
- Fixed version
2026.3.11npm install [email protected]
Advisory
Also known as: CVE-2026-32922
OpenClaw: Pairing-scoped device tokens could mint operator.admin and reach node RCE
Summary
In affected versions of openclaw, a caller holding only operator.pairing could use device.token.rotate to mint a new token with broader scopes for an already paired device. If the target device was approved for operator.admin, the attacker could obtain an administrative token without already holding administrative scope.
Impact
This is a critical authorization flaw. On deployments with connected node hosts or companion apps that expose system.run, the escalated token could then modify node execution approvals and reach real remote code execution on the node. Even without nodes, the flaw still granted unauthorized gateway-admin access.
Affected Packages and Versions
openclaw (npm)<= 2026.3.82026.3.11Technical Detailsdevice.token.rotate accepted caller-supplied target scopes and validated them against the target device's approved scopes, but it did not constrain the newly minted scopes to the caller's own current scope set. That allowed a pairing-scoped caller to mint a broader token for an already paired administrative device.
Fix
OpenClaw now enforces caller-scope subsetting in device.token.rotate, preventing callers from minting device tokens broader than the scopes they already hold. The fix shipped in [email protected].
Workarounds
Upgrade to 2026.3.11 or later.
Critical Basis: The source's own band: CRITICAL
0, fixed 2026.3.11 (semver)2026.3.11
2026.3.11npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0