GHSA-c29c-2q9c-pc86: OpenClaw: Slack allowFrom could bind to mutable display names
OpenClaw's Slack allowFrom feature could bind to mutable display names, allowing a Slack account that can change its display name metadata to match a policy entry incorrectly. This vulnerability affects versions prior to 2026.5.3. The issue does not alter OpenClaw's trusted-operator model but may allow agent access intended for another Slack identity if the feature is enabled and reachable. The vulnerability is rated high severity. Mitigations include using stable Slack user IDs in allowlists until patched, narrowing channel and tool allowlists, avoiding sharing a Gateway between untrusted users, and disabling the affected feature when not needed.
AI Analysis
Technical Summary
The vulnerability in OpenClaw's Slack allowFrom feature arises because it binds to mutable display names rather than stable identifiers. This allows a Slack account capable of changing its display name metadata to match a policy entry through this mutable data, potentially receiving agent access intended for a different Slack identity. The vulnerability does not affect the trusted-operator model of OpenClaw but depends on operator configuration and exposure of the affected feature. The first stable patched version is 2026.5.3.
Potential Impact
If the affected feature is enabled and accessible, an attacker controlling a Slack account that can change its display name could impersonate another Slack identity in policy matching, potentially gaining unintended agent access. The practical impact depends on the operator's configuration and whether lower-trust inputs can reach the vulnerable path. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix is available in OpenClaw version 2026.5.3. Until patched, operators should use stable Slack user IDs in allowlists instead of display names. Additional mitigations include keeping channel and tool allowlists narrow, avoiding sharing a Gateway between mutually untrusted users, and disabling the affected Slack allowFrom feature when it is not required.
GHSA-c29c-2q9c-pc86: OpenClaw: Slack allowFrom could bind to mutable display names
Description
OpenClaw's Slack allowFrom feature could bind to mutable display names, allowing a Slack account that can change its display name metadata to match a policy entry incorrectly. This vulnerability affects versions prior to 2026.5.3. The issue does not alter OpenClaw's trusted-operator model but may allow agent access intended for another Slack identity if the feature is enabled and reachable. The vulnerability is rated high severity. Mitigations include using stable Slack user IDs in allowlists until patched, narrowing channel and tool allowlists, avoiding sharing a Gateway between untrusted users, and disabling the affected feature when 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
The vulnerability in OpenClaw's Slack allowFrom feature arises because it binds to mutable display names rather than stable identifiers. This allows a Slack account capable of changing its display name metadata to match a policy entry through this mutable data, potentially receiving agent access intended for a different Slack identity. The vulnerability does not affect the trusted-operator model of OpenClaw but depends on operator configuration and exposure of the affected feature. The first stable patched version is 2026.5.3.
Potential Impact
If the affected feature is enabled and accessible, an attacker controlling a Slack account that can change its display name could impersonate another Slack identity in policy matching, potentially gaining unintended agent access. The practical impact depends on the operator's configuration and whether lower-trust inputs can reach the vulnerable path. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix is available in OpenClaw version 2026.5.3. Until patched, operators should use stable Slack user IDs in allowlists instead of display names. Additional mitigations include keeping channel and tool allowlists narrow, avoiding sharing a Gateway between mutually untrusted users, and disabling the affected Slack allowFrom feature when it is not required.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-c29c-2q9c-pc86
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a46eccd27e9c7971943efe5
Added to database: 07/02/2026, 22:57:17 UTC
Last enriched: 07/02/2026, 23:20:36 UTC
Last updated: 07/03/2026, 00:06:01 UTC
Views: 3
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.