CVE-2026-53824

Analyzed Analyzed - Analysis Complete

Token Revocation Bypass in OpenClaw

Publication date: 2026-06-12

Last updated on: 2026-06-16

Assigner: VulnCheck

Description

OpenClaw before 2026.4.24 contains a token revocation vulnerability allowing callers with revoked slash tokens to continue executing commands during monitor refresh windows. Attackers can exploit stale token acceptance to invoke slash command behavior briefly after token revocation, potentially executing unauthorized actions depending on operator configuration.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-06-12

Last Modified

2026-06-16

Generated

2026-07-03

AI Q&A

2026-06-13

EPSS Evaluated

2026-07-01

NVD

CVE-2026-53824

EUVD

EUVD-2026-36612

Affected Vendors & Products

Vendor	Product	Version / Range
openclaw	openclaw	to 2026.4.24 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-613	According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."

Attack-Flow Graph

Executive Summary

This vulnerability exists in OpenClaw versions before 2026.4.24 and involves a token revocation flaw. Specifically, even after a slash token is revoked, the system may still accept it briefly during monitor refresh windows. This means that an attacker with a revoked token can continue to execute commands temporarily, exploiting the acceptance of stale tokens to invoke slash command behavior.

The unauthorized execution of commands depends on the operator's configuration, potentially allowing attackers to perform actions they should no longer be authorized to do.

Impact Analysis

This vulnerability can allow attackers to execute unauthorized commands even after their access tokens have been revoked. This temporary window of acceptance for stale tokens could lead to unauthorized actions within the system, potentially compromising system integrity or security depending on the operator's configuration.

Hi! I’m here to help you understand CVE-2026-53824. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70