Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
2.3

OpenClaw lets revoked node retain Canvas access

CVE-2026-100554 · published 23 days ago
Summary

Versions of OpenClaw between May and August 2026 keep a Canvas permission active even after a paired node is removed. This lets the removed node continue to use Canvas routes until the system fully shuts down the connection. Update to version 2026.8.1 or restart the Gateway after revoking a node to stop the risk.

What to do
  • Update openclaw openclaw to version 2026.8.1 or later.
Affected software
VendorProductAffected versions
openclaw openclaw < 2026.8.1
Original advisory text
OpenClaw before 2026.8.1 Canvas Capability Revocation Bypass
OpenClaw (npm package 'openclaw') versions >= 2026.5.12 and < 2026.8.1 do not immediately invalidate Canvas HTTP authorization when a paired node is revoked. Node revocation invalidates the WebSocket client, but Canvas HTTP authorization continues to accept and renew the previously granted capability until WebSocket close cleanup completes. As a result, a revoked paired node can continue exercising its Canvas capability against the capability's configured routes during the close grace period. The issue is fixed in 2026.8.1; as a workaround, restart the Gateway after revoking a node that has Canvas access.
References
Fix within
Internet-facing 60 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker partial control
Severity
2.3 Low
Exploitation
<1% chance of attack within 30 days
Type
CWE-613Insufficient Session Expiration
Timeline
Published26 Sep 2026
Updated19 Oct 2026
First seen26 Sep 2026
Sources
CVE-2026-100554 · NVD
CVE-2026-100554 · MITRE
CVE-2026-100554 · OSV
GHSA-g697-vv6h-r8hv · GHSA
Track software like this
Free during beta