GHSA-c29c-2q9c-pc86High▾ TwilightOpenClaw: Slack allowFrom could bind to mutable display names
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 41.3 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
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.
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.
The first stable patched version is 2026.5.3.
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.
openclaw <= 2026.5.3-1Upgrade to a patched release:
openclaw 2026.5.3Connected by shared product, vendor, weakness, or advisory.
CVE-2026-53811High· 8.8OpenClaw: Matrix allowFrom could bind to mutable display names
GHSA-rggc-m335-3wvjHighOpenClaw: Same-host trusted-proxy deployments could accept local forged identity headers
CVE-2026-53817High· 8.0OpenClaw: Control UI locality spoofing could mint a durable admin device token
GHSA-p44v-rx83-vjp4High· 8.1Duplicate Advisory: Discord allowFrom could bind to mutable display names
GHSA-w7m7-3xcf-mp48High· 8.1Duplicate Advisory: Zalo allowFrom could bind to mutable display names
CVE-2026-53857High· 8.1OpenClaw: Zalo allowFrom could bind to mutable display names