Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with exec-level credentials
-
DeliveryAccess Slack plugin approval interface
-
ExploitSubmit resolution via exec approver gate
-
ExecutionBypass operator-defined approval split
-
ImpactApprove plugin actions outside authorized scope
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
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 the attacker to already hold exec-authorized user credentials within OpenClaw (confirmed by PR:L in the CVSS 4.0 vector - unauthenticated exploitation is not possible). The Slack plugin must be deployed and operator-configured with approval splits; the CVSS 4.0 AT:P metric explicitly encodes this prerequisite. Exploitation is further limited by: (1) the impact ceiling of VC:L only - no integrity or availability impact is achievable through this path; (2) the need for an active Slack plugin integration, which is not a default or universal deployment; and (3) the attacker must already be a recognized user within the system with at least exec-tier permissions, making this an insider-threat or account-compromise scenario rather than an opportunistic external attack. Organizations not using the Slack plugin, or using it without approval splits, are not exposed. |
| Impact | Multiple risk signals converge on a low-priority assessment. The CVSS 4.0 base score of 2.3 is driven by three compounding limiters: AT:P (specific prerequisites required), PR:L (attacker must already hold exec-level authentication), and a constrained impact profile of VC:L/VI:N/VA:N - meaning only limited confidentiality exposure on the vulnerable system, with no integrity or availability impact. This is inconsistent with a traditional privilege escalation that grants elevated system access; the 'escalation' here is confined to the approval workflow itself. No EPSS data was provided. The vulnerability is not listed in CISA KEV and no POC has been identified. Real-world risk is essentially an insider-threat or privilege-abuse scenario within organizations running OpenClaw with Slack plugin approval splits - the attack surface is not reachable in default or Slack-plugin-less deployments. The tags 'Authentication Bypass' and 'Privilege Escalation' from VulnCheck are accurate but may overstate severity without the configuration context. |
| Exploit ScenarioDerived | An insider or compromised account holding exec-authorized user status in OpenClaw navigates to the Slack plugin approval interface and submits a resolution request through the exec approver gate for a plugin action they are not operator-configured to approve. The system incorrectly authorizes the resolution, allowing the user to approve plugin actions outside the operator-defined split - potentially triggering plugin behaviors that were intended to require multi-party sign-off. No public POC has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 29, 2026
Privilege escalation in OpenClaw's Slack plugin approval workflow allows authenticated users holding limited exec permissions to bypass operator-configured approval splits by resolving plugin approvals through the exec approver gate - approving actions outside their intended authorization boundary. All OpenClaw versions before 2026.5.12 are affected when the Slack plugin is deployed with approval split configurations. No public exploit code has been identified and this vulnerability is not listed in CISA KEV; the CVSS 4.0 score of 2.3 accurately reflects its narrow real-world impact, constrained by prerequisites and a low impact ceiling.
RemediationAI
Upgrade to OpenClaw 2026.5.12 or later, which resolves the incorrect authorization in the exec approver gate per the vendor advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-wv26-j37q-2g7p. For deployments that cannot immediately upgrade, restrict exec approval permissions to only fully trusted personnel, which eliminates the risk surface by ensuring no potentially malicious insider holds exec-level authorization. Operators should also audit existing Slack plugin approval split configurations to verify that sensitive plugin actions require approval from roles beyond the exec gate alone - adding a secondary, independent approval role as a workaround trade-off (increased approval friction in exchange for authorization boundary enforcement). Note that disabling the Slack plugin entirely removes the attack surface without affecting non-Slack functionality.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in npm
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
OpenClaw implements a multi-party authorization model for Slack plugin actions using configurable 'approval splits' - operator-defined gates that distribute resolution authority among distinct roles to enforce separation of duties. The exec approver gate is one such gate, intended for a specific tier of approval authority. CWE-863 (Incorrect Authorization) describes the root cause: the system incorrectly evaluates whether an exec-authorized user holds sufficient rights to resolve approvals through that gate, failing to enforce the operator-intended split. The CVSS 4.0 AT:P (Attack Requirements: Present) metric directly encodes that the vulnerability is only reachable under a specific deployment configuration - Slack plugin active with approval splits configured. No CPE strings were provided in the available intelligence; affected scope is derived from the vendor advisory and description alone.
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
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Primary rating from Vendor (vulncheck) · only source for this CVE.
CVSS VectorVendor: vulncheck
Lifecycle Timeline
1DescriptionCVE.org
OpenClaw before 2026.5.12 contains a privilege escalation vulnerability in Slack plugin approvals that allows exec-authorized users to resolve plugin approvals through the exec approver gate. Attackers with limited exec approval permissions can bypass intended approval splits to approve plugin actions outside operator configuration.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Auth bypass in OpenClaw voice-call extension before 2026.2.1. EPSS 0.68%. PoC and patch available.
Privilege escalation in OpenClaw (pre-2026.3.28) allows unauthenticated remote attackers to gain administrative access b
OpenClaw versions 2026.2.22 through 2026.2.24 contain a privilege escalation vulnerability that allows authenticated att
An authorization mismatch vulnerability in OpenClaw versions prior to 2026.3.1 allows authenticated users with operator.
OpenClaw versions prior to 2026.1.29 automatically establish WebSocket connections to attacker-controlled gateway URLs e
Path traversal in OpenClaw through version 2026.3.23 enables unauthenticated remote attackers to read arbitrary files in
Authentication bypass in OpenClaw before 2026.5.3 allows remote attackers with low privileges to receive agent responses
Directory-context bypass in OpenClaw before 2026.8.1 allows authenticated attackers with user interaction to reuse an 'a
Unauthenticated access to the noVNC observer interface in OpenClaw's Docker sandbox browser allows anyone who can reach
OpenClaw versions before 2026.2.26 allow authenticated attackers to write arbitrary files outside the workspace director
OpenClaw versions prior to 2026.2.22 contain a shell environment variable injection vulnerability in the system.run func
OpenClaw versions prior to 2026.2.22 contain a resource exhaustion vulnerability where the application fails to consiste
EUVD-2026-33333
GHSA-6c56-hgvp-5v87
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB