CVE-2026-53824: OpenClaw · Mattermost slash token revocation could lag until monitor refresh
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 6.3 Medium : upgrade to 2026.4.24 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.4.24
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.4.24.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in version 2026.4.24. Until patched, operators should restart or refresh the Mattermost monitor after token rotation to prevent lag in token revocation. Additionally, operators should keep channel and tool allowlists narrow, avoid sharing one Gateway between mutually untrusted users, and disable the affected feature when it is not needed.
Description
Mattermost slash token revocation in OpenClaw CLI could lag until the monitor refreshes, allowing brief acceptance of revoked tokens. This affects versions from 2026.1.29 up to but not including 2026.4.24. The issue occurs only when the affected feature is enabled and reachable, with impact depending on operator configuration and trust boundaries. A patch is available in version 2026.4.24. Mitigation includes restarting or refreshing the Mattermost monitor after token rotation until patched, and applying configuration hardening such as narrow allowlists and disabling the feature if not needed.