OpenClaw: Slack allowFrom could bind to mutable display names
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-290.
Summary
### Summary Slack allowFrom could bind to mutable display names. In affected versions, a Slack account able to change display name metadata could match a policy entry through mutable display metadata. This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed. ### Impact When the affected feature is enabled and reachable, this could receive agent access intended for another Slack identity. Practical impact depends on the operator's configuration and whether lower-trust input can reach that path. ### Patched Versions The first stable patched version is `2026.5.3`. ### Mitigations use stable Slack user IDs in allowlists until patched. As general hardening, keep channel and tool allowlists narrow, avoid sharing one Gateway between mutually untrusted users, and disable the affected feature when it is not needed.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | openclaw (npm) | before 2026.5.3 | 2026.5.3 | Patch available | GHSA-c29c-2q9c-pc86 |
- openclaw (npm) Vendor— Affected before 2026.5.3 Fixed in 2026.5.3 Patch available GHSA-c29c-2q9c-pc86
Remediation
- Fix · GHSA-c29c-2q9c-pc86 openclaw (npm) Fixed in 2026.5.3 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-c29c-2q9c-pc86
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences