GHSA-4m3v-q747-pc6h: OpenClaw: Mattermost slash token revocation could lag until monitor refresh
OpenClaw versions prior to 2026.4.24 have a vulnerability where Mattermost slash token revocation may not take immediate effect, allowing a revoked token to be accepted until the monitor refreshes. This issue affects the slash command feature when enabled and reachable. The vulnerability does not affect the overall trusted-operator model of OpenClaw. The practical impact depends on configuration and exposure to lower-trust inputs. A fix is available starting with version 2026.4.24. Until patched, restarting or refreshing the Mattermost monitor after token rotation mitigates the issue. Additional hardening includes restricting channel and tool allowlists, avoiding shared Gateways among untrusted users, and disabling the feature if not needed.
AI Analysis
Technical Summary
OpenClaw's Mattermost slash token revocation can lag until the monitor refreshes, allowing a caller with an old token to continue using it during this window. This vulnerability affects versions before 2026.4.24. The issue is scoped to the slash command feature and does not alter the trusted-operator security model. The impact depends on operator configuration and exposure to untrusted inputs. The vulnerability is classified under CWE-613 (Insufficient Session Expiration). The first stable patched version is 2026.4.24.
Potential Impact
When the affected feature is enabled and accessible, revoked Mattermost slash tokens may still be accepted briefly until the monitor refreshes. This could allow slash command behavior to be invoked with a revoked token during that window. The actual impact depends on the operator's configuration and whether untrusted inputs can reach the affected path. There are no known exploits in the wild.
Mitigation Recommendations
A fix is available in OpenClaw version 2026.4.24. Until systems are updated, operators should restart or refresh the Mattermost monitor after token rotation to ensure revoked tokens are no longer accepted. Additionally, it is recommended to keep channel and tool allowlists narrow, avoid sharing a Gateway between mutually untrusted users, and disable the affected feature when it is not needed.
GHSA-4m3v-q747-pc6h: OpenClaw: Mattermost slash token revocation could lag until monitor refresh
Description
OpenClaw versions prior to 2026.4.24 have a vulnerability where Mattermost slash token revocation may not take immediate effect, allowing a revoked token to be accepted until the monitor refreshes. This issue affects the slash command feature when enabled and reachable. The vulnerability does not affect the overall trusted-operator model of OpenClaw. The practical impact depends on configuration and exposure to lower-trust inputs. A fix is available starting with version 2026.4.24. Until patched, restarting or refreshing the Mattermost monitor after token rotation mitigates the issue. Additional hardening includes restricting channel and tool allowlists, avoiding shared Gateways among untrusted users, and disabling the feature if not needed.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
OpenClaw's Mattermost slash token revocation can lag until the monitor refreshes, allowing a caller with an old token to continue using it during this window. This vulnerability affects versions before 2026.4.24. The issue is scoped to the slash command feature and does not alter the trusted-operator security model. The impact depends on operator configuration and exposure to untrusted inputs. The vulnerability is classified under CWE-613 (Insufficient Session Expiration). The first stable patched version is 2026.4.24.
Potential Impact
When the affected feature is enabled and accessible, revoked Mattermost slash tokens may still be accepted briefly until the monitor refreshes. This could allow slash command behavior to be invoked with a revoked token during that window. The actual impact depends on the operator's configuration and whether untrusted inputs can reach the affected path. There are no known exploits in the wild.
Mitigation Recommendations
A fix is available in OpenClaw version 2026.4.24. Until systems are updated, operators should restart or refresh the Mattermost monitor after token rotation to ensure revoked tokens are no longer accepted. Additionally, it is recommended to keep channel and tool allowlists narrow, avoid sharing a Gateway between mutually untrusted users, and disable the affected feature when it is not needed.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-4m3v-q747-pc6h
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 4.0
Threat ID: 6a46ecc627e9c7971943d977
Added to database: 07/02/2026, 22:57:10 UTC
Last enriched: 07/02/2026, 23:19:11 UTC
Last updated: 07/02/2026, 23:19:11 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.