OpenClaw versions from 2026.5.12 up to but not including 2026.8.1 possess a flaw that allows a revoked paired node to continue using an existing Canvas HTTP capability. When a node is revoked, the WebSocket client is closed, but the HTTP authorization tokens are not immediately invalidated. The client can still renew these tokens and retain access to the Canvas endpoint until the WebSocket close–cleanup routine completes. This failure to revoke the capability could let an attacker retain unauthorized access to the Canvas service and perform actions permitted by the capability, thereby compromising the service’s integrity or confidentiality within the scope of that capability.

The vulnerability impacts the OpenClaw software distributed as the npm package 'openclaw'. All versions whose release dates fall between 2026.5.12 (inclusive) and 2026.8.1 (exclusive) are affected. The package name is OpenClaw, and the product is identified by the OpenClaw CNA. No additional vendor or platform variants are listed.

The CVSS score for this issue is 2.3, indicating a low overall severity. No EPSS score is available, so the current likelihood of exploitation is unclear, but the potential for misuse exists if the revocation mechanism is abused. The vulnerability is not listed in the CISA KEV catalog. Based on the description, the likely attack vector is internal: an entity with the ability to trigger node revocation or to observe the revocation event can realize that the HTTP capability remains valid for a short window. Exploitation requires neither remote code execution nor external access; it hinges on the revocation logic itself.