Skip to main content

OpenClaw Slack EUVDEUVD-2026-87476

| CVE-2026-100575 HIGH
Missing Authorization (CWE-862)
2026-09-26 VulnCheck GHSA-p6pm-6pmc-m53c
8.7
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Join multi-person Slack DM with agent
  2. Delivery
    Send message despite allowlist exclusion
  3. Exploit
    Agent processes disallowed sender
  4. Execution
    Invoke granted tools and read data
  5. Impact
    Access confidentiality/integrity of agent resources

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires: (1) an OpenClaw Slack agent deployed with a configured sender allowlist policy (the feature being bypassed); (2) the attacker to be a participant in a multi-person / group direct message that includes that agent - so the attacker must be an authenticated Slack workspace user who was intentionally excluded from the allowlist; and (3) the affected version being before 2026.8.1. The concrete flaw is that allowlist enforcement is skipped specifically in multi-person DMs, not 1:1 DMs. Impact is limited by the scope of tools and data granted to the targeted agent - a read-only agent yields only data disclosure, whereas an agent with command/write tools yields far greater impact. No end-user interaction on the victim side is required.

Impact

The vendor CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H) rates this 8.7 (High), and this is broadly defensible for the exploit mechanics: the attack is network-reachable through Slack, low-complexity, and requires only low privilege (PR:L) - the attacker must be a participant in a multi-person direct message, i.e. an authenticated Slack user who was NOT on the agent's sender allowlist. No user interaction is needed (UI:N). The realistic technical impact, however, is bounded by whatever tools and data the targeted Slack agent has been granted; the vendor's VC:H/VI:H/VA:H assumes a highly-privileged agent (e.g. one with command or write tools), which will not hold for every deployment, so I assess impact slightly lower and availability as limited (see my vector). This is CWE-862 missing authorization (an authorization/allowlist bypass), not true authentication bypass despite the input tag. On real-world priority: EPSS is not provided, there is NO CISA KEV listing and NO public POC identified in the input, so there is no evidence of active or automated exploitation - this is a real but not urgent issue. The dominant risk-limiting factor is product prevalence: OpenClaw is a niche open-source agent framework, so despite the high CVSS this is a targeted, low-widespread-exposure concern rather than a mass-exploitation priority. Key missing data: EPSS score and any independent exploitation telemetry.

Exploit ScenarioDerived

An attacker who holds a valid Slack account but is deliberately excluded by the agent's configured sender allowlist gets added to (or participates in) a multi-person/group direct message that includes an OpenClaw Slack agent. Because the allowlist is not enforced for group DMs, the attacker sends a message that the agent processes, invoking whatever tools and reading whatever data that agent is authorized to use. No public exploit code is identified at time of analysis; exploitation requires only a Slack message, no user interaction on the victim side.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 26, 2026

OpenClaw Slack deployments before 2026.8.1 fail to enforce configured sender allowlists inside multi-person (group) direct messages, allowing an authenticated Slack workspace user who was deliberately excluded from the allowlist to invoke the Slack agent and reach every tool and data source that agent has been granted. Because the bypass is confined to group DMs rather than 1:1 conversations, any excluded participant who shares a multi-person DM with the agent can trigger it without victim-side interaction; the practical blast radius depends entirely on the agent's privileges, ranging from data disclosure on a read-only agent to full command/write capability on a more powerful one. The vendor rates this 8.7 (CVSS 4.0, AV:N/AC:L/AT:N/PR:L/UI:N with high confidentiality, integrity and availability impact), an assessment our independent review considers broadly defensible for the mechanics; no public exploit code and no confirmed active exploitation were identified at time of analysis, though EPSS and KEV data were not provided.

RemediationAI

Upgrade OpenClaw Slack to 2026.8.1 or later, the version in which allowlist enforcement in multi-person direct messages is corrected - vendor-released patch: 2026.8.1 - following the guidance in the upstream advisory GHSA-58qx-6m8p-wh2j (https://github.com/openclaw/openclaw/security/advisories/GHSA-58qx-6m8p-wh2j) and the VulnCheck advisory (https://www.vulncheck.com/advisories/openclaw-slack-before-2026.8.1-authentication-bypass-via-group-dm). If immediate upgrade is not possible, treat group DMs as an untrusted invocation path: remove the agent from multi-person DMs and restrict its membership to monitored 1:1 conversations until patched - the trade-off is loss of legitimate multi-party agent workflows - or, if the platform allows it, disable group-DM handling for the agent entirely. In parallel, reduce the agent's granted tool and data scope to the minimum required (read-only where feasible), since the bypass inherits whatever privileges the agent holds and narrowing them caps the worst-case impact without restoring the broken allowlist. Audit Slack workspace membership and existing group DMs containing OpenClaw agents, review agent invocation logs for unexpected senders, and confirm that no alternate invocation path (for example direct API or webhook entry points) shares the same skipped authorization check.

Affected VersionsENISA

Slack 0 <2026.8.1

Affected Packages

euvd slack fix: 2026.8.1

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is a missing-authorization-check class issue (CWE-862), rooted in inconsistent policy enforcement across Slack conversation contexts. OpenClaw Slack exposes an agent to workspace users and relies on a configured sender allowlist to gate who may invoke it and which downstream tools/data the agent may reach. That enforcement path is correctly applied to 1:1 direct messages but is skipped when the conversation is a multi-person (group) DM, so the identity check that would otherwise reject a non-allowlisted sender never runs and the agent processes the request as if authorized. The affected component is tracked under CPE cpe:2.3:a:openclaw:slack:*:*:*:*:*:*:*:* with all versions prior to 2026.8.1 vulnerable. Slack's group DM model is relevant: membership is user-driven, so an excluded actor can be added to (or already sit in) a group DM alongside the agent and thereby satisfy the implicit 'participant' precondition. The root cause is authorization logic keyed on conversation type rather than a single centralized, context-independent allowlist decision, which is why the same policy is honored in one channel shape and ignored in another. Impact is scoped to whatever the targeted agent is provisioned to do - read-only tools limit the outcome to information disclosure, while agents holding command execution, ticketing, file, or messaging tools can be driven to state-changing actions.

Know when Openclaw gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 8.7 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 8.3 HIGH

PR:L because the attacker must be an authenticated Slack participant in the group DM; C:H/I:H reflect access to agent tools/data, A:L since availability impact depends on granted tools.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Sep 26, 2026 - 03:01 EUVD
CVE Published
Sep 26, 2026 - 02:19 cve.org
HIGH 8.7

DescriptionCVE.org

OpenClaw Slack versions before 2026.8.1 fail to properly enforce sender allowlists in multi-person direct messages. Disallowed participants can trigger Slack agents and access tools and data granted to those agents by bypassing configured sender policies.

Technical POC Analysis

CWE-862 (Missing Authorization); the advisory also tags CWE-863 (Incorrect Authorization).

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

OpenClaw Slack deployments prior to version 2026.8.1 fail to enforce sender allowlists in group direct messages, enabling an authenticated workspace user who was explicitly excluded to invoke the Slack agent and access all its connected tools and data. This vulnerability could result in unauthorized data disclosure or system modifications, with the blast radius depending on the agent's privileges; leadership should care because it directly threatens data confidentiality and operational integrity. No public exploit identified at time of analysis, but the high severity underscores the need for immediate mitigation.

Business Impact: High
Compensating Controls

Disable group DM functionality for the Slack agent, enforce least privilege on agent permissions, monitor group DM activity for anomalies, and use an external proxy to validate sender allowlists.

Threat Intelligence Overview

EPSS Score
0.3%
Top 84% exploitable
Prevalence
Low
niche open-source AI agent framework, minimal enterprise footprint
Social Media
5
Sightings
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2026-28446 CRITICAL POC
9.4 Mar 05

Auth bypass in OpenClaw voice-call extension before 2026.2.1. EPSS 0.68%. PoC and patch available.

CVE-2026-33579 CRITICAL POC
9.4 Mar 31

Privilege escalation in OpenClaw (pre-2026.3.28) allows unauthenticated remote attackers to gain administrative access b

CVE-2026-32042 HIGH POC
8.8 Mar 21

OpenClaw versions 2026.2.22 through 2026.2.24 contain a privilege escalation vulnerability that allows authenticated att

CVE-2026-32051 HIGH POC
8.8 Mar 21

An authorization mismatch vulnerability in OpenClaw versions prior to 2026.3.1 allows authenticated users with operator.

CVE-2026-25253 HIGH POC
8.8 Feb 01

OpenClaw versions prior to 2026.1.29 automatically establish WebSocket connections to attacker-controlled gateway URLs e

CVE-2026-32846 HIGH POC
8.7 Mar 26

Path traversal in OpenClaw through version 2026.3.23 enables unauthenticated remote attackers to read arbitrary files in

CVE-2026-100530 HIGH POC
8.5 Sep 26

Directory-context bypass in OpenClaw before 2026.8.1 allows authenticated attackers with user interaction to reuse an 'a

CVE-2026-32064 HIGH POC
8.5 Mar 21

Unauthenticated access to the noVNC observer interface in OpenClaw's Docker sandbox browser allows anyone who can reach

CVE-2026-32055 HIGH POC
7.6 Mar 21

OpenClaw versions before 2026.2.26 allow authenticated attackers to write arbitrary files outside the workspace director

CVE-2026-32056 HIGH POC
7.5 Mar 21

OpenClaw versions prior to 2026.2.22 contain a shell environment variable injection vulnerability in the system.run func

CVE-2026-32049 HIGH POC
7.5 Mar 21

OpenClaw versions prior to 2026.2.22 contain a resource exhaustion vulnerability where the application fails to consiste

CVE-2026-32048 HIGH POC
7.5 Mar 21

OpenClaw versions prior to 2026.3.1 contain a sandbox escape vulnerability that allows authenticated attackers with low

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy