CVE-2026-100554 in OpenClaw
Summary
by MITRE • 09/26/2026
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.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 09/26/2026
The vulnerability identified within OpenClaw versions ranging from 2026.5.12 up to but not including 2026.8.1 represents a critical authorization state synchronization failure in distributed systems utilizing paired nodes for canvas operations. This flaw specifically affects the handling of HTTP-based Canvas authentication when a node is revoked by an administrator or system process. In this architecture, OpenClaw manages access control through two distinct communication channels: WebSocket connections used primarily for real-time updates and command execution, and HTTP endpoints utilized for standard RESTful interactions with the canvas capability. The security model relies on the immediate invalidation of all active credentials associated with a revoked node to prevent unauthorized persistence of access rights.
The technical root cause lies in an asynchronous cleanup mechanism that fails to propagate revocation status across different protocol handlers instantaneously. When a paired node is revoked, the system correctly terminates the WebSocket client connection and updates the internal state for real-time communication channels. However, the HTTP authorization middleware continues to validate tokens or session identifiers associated with the now-revoked node against its configured routes. The validation logic does not check the revocation status in real time but instead relies on cached states that are only refreshed during specific lifecycle events. Consequently, there exists a window of opportunity where previously granted capabilities remain active and renewable for HTTP requests originating from the revoked node.
This discrepancy creates a significant operational impact characterized by an authorization bypass vulnerability. An attacker who has compromised or controls a paired node can continue to exercise canvas privileges even after revocation is initiated. This persistence allows for continued data exfiltration, unauthorized modification of canvas content, or further lateral movement within the system during the grace period before WebSocket close cleanup completes. The severity is compounded by the fact that HTTP requests are often stateless and may not trigger immediate re-authentication checks against the central authorization server in the same way interactive sessions do. This allows malicious actors to maintain a foothold and perform actions under the guise of legitimate, previously authorized operations long after access should have been terminated.
From an industry standard perspective, this vulnerability aligns with CWE-613, which describes insufficient session expiration, as well as CWE-284 regarding improper access control where authorization checks are not consistently applied across all components of a system. In the context of the MITRE ATT&CK framework, this behavior facilitates Persistence and Defense Evasion techniques by allowing an adversary to maintain access through lingering valid credentials despite administrative revocation efforts. The failure to immediately invalidate tokens or session states upon account compromise or node removal is a common pattern in systems that do not implement centralized, real-time token validation for all protocol types.
To mitigate this risk, organizations running affected versions of OpenClaw should upgrade to version 2026.8.1 or later as soon as possible, which resolves the synchronization delay between WebSocket and HTTP authorization states. For environments where immediate upgrading is not feasible, a manual workaround involves restarting the Gateway service immediately after revoking any node that possesses Canvas access privileges. This restart forces a complete reset of all in-memory state, including cached authentication tokens and session data, thereby ensuring that no stale credentials remain active for revoked nodes. Regular audits of paired node permissions and monitoring for unexpected HTTP activity from recently disconnected WebSocket clients can also help detect exploitation attempts during the vulnerability window.