CVE-2026-32895: OpenClaw: Slack system events bypass sender authorization in member and message subtype handlers
OpenClaw up to 2026.2.25 queued Slack member join/leave events and message subtype events (message_changed, message_deleted, thread_broadcast) as system events without checking the sender against the allowlists. Non-allowlisted Slack users could feed events to the agent. Upgrade openclaw to 2026.2.26.
Published Mar 12, 2026 · Updated Mar 30, 2026 · Analysis Oct 31, 2026
What an attacker can do
The Slack handlers in src/slack/monitor/events/members.ts and messages.ts did a channel check and then enqueued the system event. They skipped the shared sender authorization that ordinary Slack messages go through. Deployments that rely on Slack DM allowlists (dmPolicy and allowFrom) or per-channel users allowlists could therefore take in system events from people who were not on those lists.
The weakness is incorrect authorization (CWE-863). The advisory rates it network, low privileges, with low confidentiality and integrity impact. The attacker needs to be a Slack user who can reach the bot, such as a member of a workspace or channel it watches. They cannot send normal messages to the agent, but they can trigger edits, deletions, thread broadcasts or join and leave events that the agent logs as system events. For an AI agent that reads its event queue as context, this is an unauthorized input channel, and it can be used to plant text the operator never approved.
Who is affected
The openclaw npm package up to and including 2026.2.25, in deployments that connect Slack and rely on dmPolicy, allowFrom or per-channel users allowlists to control who can interact.
npm ls -g openclaw
openclaw --versionOpen-policy deployments gain nothing from the allowlists in the first place.
openclaw
- Ecosystem
- npm
- Affected
- <= 2026.2.25
- Fixed in
- 2026.2.26
- Check
npm ls openclaw
How to fix it
Upgrade to openclaw 2026.2.26 or later.
npm install -g openclaw@latestThe fix (commit 3d30ba1) sends these handlers through authorizeAndResolveSlackSystemEventContext, the same gate regular messages use. Message subtype events now fail closed when the sender identity cannot be resolved. Tests confirm that events are blocked when DMs are disabled, when the sender is not on the allowlist, and when the user is outside a channel's users list. The sources give no workaround.
How to tell if you were hit
Review OpenClaw's Slack system-event logs for member_joined, member_left, message_changed, message_deleted or thread_broadcast events from user IDs that are not in your allowFrom or users allowlists. Events from unlisted users that were enqueued, and any agent action that followed them, indicate the gap was used. Beam records the shell commands and file access of agents, which shows what an agent did after such an event.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Summary
Slack member_* and message subtype system events (message_changed, message_deleted, thread_broadcast) were not consistently enforcing sender authorization before enqueueing system events.
Affected Packages / Versions
- Package:
openclaw(npm) - Latest published version:
2026.2.25 - Affected range:
<= 2026.2.25 - Planned patched version:
2026.2.26(pre-set for publish-readiness)
Technical Details
Slack system-event handlers in src/slack/monitor/events/members.ts and src/slack/monitor/events/messages.ts enqueued events after channel checks without shared sender authorization. Deployments relying on Slack DM allowlists (dmPolicy / allowFrom) or per-channel users allowlists could receive unauthorized system-event ingress from non-allowlisted senders.
The fix routes those handlers through authorizeAndResolveSlackSystemEventContext(...) and fails closed when message subtype sender identity cannot be resolved.
Fix Commit(s)
3d30ba18a2aba1e1b302e77ff33145c3b06c01c8
Release Process Note
patched_versions is pre-set to >= 2026.2.26 so once npm 2026.2.26 is published, this advisory can be published without further field edits.
Thanks @tdjackey for reporting.
Credited to tdjackey.
Questions
- Which Slack events were affected by CVE-2026-32895?
Member join and leave events, plus the message subtypes message_changed, message_deleted and thread_broadcast. Regular messages already passed sender authorization.
- Does it matter if I use allowlists?
Yes, that is the exposed case. Deployments using dmPolicy, allowFrom or per-channel users allowlists could receive system events from non-allowlisted senders.
- Which version fixes it?
openclaw 2026.2.26. Versions up to 2026.2.25 are affected.
References
Read for this analysis:
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More OpenClaw vulnerabilities
All OpenClaw entriesCVE-2026-62197
OpenClaw: Browser CDP discovery could accept blocked WebSocket URLs
medium8.5Oct 21, 2026CVE-2026-35630
OpenClaw: QQBot native approval buttons did not enforce configured approver identity
high8.0Jul 2, 2026CVE-2026-53806
OpenClaw: Combined POSIX shell options could confuse exec revalidation
high8.8Jul 2, 2026CVE-2026-53809
OpenClaw: Embedded runner policy could be confused by provider aliases
medium3.8Jul 2, 2026CVE-2026-53810
OpenClaw's marketplace runtime extension metadata could point at unscanned payloads
high8.8Jul 2, 2026CVE-2026-53811
OpenClaw: Matrix allowFrom could bind to mutable display names
high8.8Jul 2, 2026
