Slack group DMs could skip sender allowlists
GHSA-58qx-6m8p-wh2j · published 2026-09-11
- Severity
- High
- CVSS score
- 8.8
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 2026.8.1
When a Slack agent was present in a group DM, a disallowed participant could trigger the agent within the tools and data already granted to that agent. Practical impact depends on the agent's tool policy and channel configuration.
Upgrade @openclaw/slack to 2026.8.1 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
The first stable patched version is 2026.8.1.
upgrade to @openclaw/[email protected] or later. Until upgraded, do not add tool-enabled agents to multi-person direct messages containing untrusted participants.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @openclaw/slack | npm | < 2026.8.1 | 2026.8.1 |
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
- MediumSlack file downloads could miss conversation authorization@openclaw/slack
The impact, patch and workaround text comes from the advisory, shortened (published by OpenClaw). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.