GHSA-275c-xpvc-jgfw: OpenClaw: Slack and Zalo webhook secrets could remain active after secrets.reload
OpenClaw versions prior to 2026.4.22 have a vulnerability where Slack and Zalo webhook secrets may remain active after a secrets.reload operation. This allows a caller with an old webhook secret to continue sending webhook events during a brief stale-secret window after secret rotation. The vulnerability affects the webhook secret revocation process but does not alter OpenClaw's trusted-operator security model. The impact depends on the operator's configuration and exposure of the affected feature. A fix is available starting with version 2026.4.22.
AI Analysis
Technical Summary
In OpenClaw versions before 2026.4.22, a flaw exists in the handling of Slack and Zalo webhook secrets such that after invoking secrets.reload, old webhook secrets may remain valid for a short period. This stale-secret window allows webhook events to be accepted using revoked secrets, potentially delivering events after the operator expects revocation. The issue is scoped to the webhook secret management feature and does not affect the overall trusted-operator model of OpenClaw. The vulnerability is classified under CWE-613 (Insufficient Session Expiration).
Potential Impact
The vulnerability allows webhook events to be accepted briefly after secret rotation, potentially enabling unauthorized webhook calls during the stale-secret window. The practical impact depends on the operator's configuration, the exposure of the affected webhook feature, and whether lower-trust inputs can reach the webhook processing path. There are no known exploits in the wild. The severity is moderate.
Mitigation Recommendations
A fixed version is available starting with OpenClaw 2026.4.22. Until upgrading, operators should restart the affected channel runtime after rotating webhook secrets to ensure old secrets are invalidated. Additional mitigations include maintaining narrow channel and tool allowlists, avoiding sharing a Gateway between mutually untrusted users, and disabling the affected webhook feature when not needed.
GHSA-275c-xpvc-jgfw: OpenClaw: Slack and Zalo webhook secrets could remain active after secrets.reload
Description
OpenClaw versions prior to 2026.4.22 have a vulnerability where Slack and Zalo webhook secrets may remain active after a secrets.reload operation. This allows a caller with an old webhook secret to continue sending webhook events during a brief stale-secret window after secret rotation. The vulnerability affects the webhook secret revocation process but does not alter OpenClaw's trusted-operator security model. The impact depends on the operator's configuration and exposure of the affected feature. A fix is available starting with version 2026.4.22.
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
In OpenClaw versions before 2026.4.22, a flaw exists in the handling of Slack and Zalo webhook secrets such that after invoking secrets.reload, old webhook secrets may remain valid for a short period. This stale-secret window allows webhook events to be accepted using revoked secrets, potentially delivering events after the operator expects revocation. The issue is scoped to the webhook secret management feature and does not affect the overall trusted-operator model of OpenClaw. The vulnerability is classified under CWE-613 (Insufficient Session Expiration).
Potential Impact
The vulnerability allows webhook events to be accepted briefly after secret rotation, potentially enabling unauthorized webhook calls during the stale-secret window. The practical impact depends on the operator's configuration, the exposure of the affected webhook feature, and whether lower-trust inputs can reach the webhook processing path. There are no known exploits in the wild. The severity is moderate.
Mitigation Recommendations
A fixed version is available starting with OpenClaw 2026.4.22. Until upgrading, operators should restart the affected channel runtime after rotating webhook secrets to ensure old secrets are invalidated. Additional mitigations include maintaining narrow channel and tool allowlists, avoiding sharing a Gateway between mutually untrusted users, and disabling the affected webhook feature when not needed.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-275c-xpvc-jgfw
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 4.0
Threat ID: 6a46ecc627e9c7971943d981
Added to database: 07/02/2026, 22:57:10 UTC
Last enriched: 07/02/2026, 23:19:25 UTC
Last updated: 07/03/2026, 02:26:43 UTC
Views: 6
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.