https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 20:49:57 +0000 https://cve.radiocsirt.org/vuln/cve-2026-32922 <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw before 2026.3.11 contains a privilege escalation vulnerability in device.token.rotate that allows callers with operator.pairing scope to mint tokens with broader scopes by failing to constrain newly minted scopes to the caller&#39;s current scope set. Attackers can obtain operator.admin tokens for paired devices and achieve remote code execution on connected nodes via system.run or gain unauthorized gateway-admin access.</p> <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw before 2026.3.11 contains a privilege escalation vulnerability in device.token.rotate that allows callers with operator.pairing scope to mint tokens with broader scopes by failing to constrain newly minted scopes to the caller&#39;s current scope set. Attackers can obtain operator.admin tokens for paired devices and achieve remote code execution on connected nodes via system.run or gain unauthorized gateway-admin access.</p> https://cve.radiocsirt.org/vuln/cve-2026-32922 https://cve.radiocsirt.org/vuln/ghsa-4jpw-hj22-2xmc <p><strong>Affected:</strong> npm: openclaw</p> <p>## 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.</p> <p>## 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.</p> <p>## Affected Packages and Versions - Package: `openclaw` (npm) - Affected versions: `&lt;= 2026.3.8` - Fixed in: `2026.3.11`</p> <p>## Technical Details `device.token.rotate` accepted caller-supplied target scopes and validated them against the target device&#39;s approved scopes, but it did not constrain the newly minted scopes to the caller&#39;s own current scope set. That allowed a pairing-scoped caller to mint a broader token for an already paired administrative device.</p> <p>## 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 `openclaw@2026.3.11`.</p> <p>## Workarounds Upgrade to `2026.3.11` or later.</p> <p><strong>Affected:</strong> npm: openclaw</p> <p>## 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.</p> <p>## 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.</p> <p>## Affected Packages and Versions - Package: `openclaw` (npm) - Affected versions: `&lt;= 2026.3.8` - Fixed in: `2026.3.11`</p> <p>## Technical Details `device.token.rotate` accepted caller-supplied target scopes and validated them against the target device&#39;s approved scopes, but it did not constrain the newly minted scopes to the caller&#39;s own current scope set. That allowed a pairing-scoped caller to mint a broader token for an already paired administrative device.</p> <p>## 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 `openclaw@2026.3.11`.</p> <p>## Workarounds Upgrade to `2026.3.11` or later.</p> https://cve.radiocsirt.org/vuln/ghsa-4jpw-hj22-2xmc