Skip to main content
EPSS 0.6%top 53%

Openclaw cli: OpenClaw Slack: dmPolicy=open allowed any DM sender to run privileged slash commands (CVE-2026-28392)

0
Medium
Published: 08/13/2026 (08/13/2026, 17:21:32 UTC)
Source: GCVE Database
Product: openclaw-cli

Description

A vulnerability in the openclaw CLI's Slack integration allowed any Slack user who could send a direct message to the bot to execute privileged slash commands when the Slack DM policy was set to open. This bypassed intended allowlist and access-group restrictions. The issue affects openclaw versions from 2026.1.29 up to but not including 2026.2.14 when configured with dmPolicy=open. A patch is available in version 2026.2.14 that corrects the authorization logic for direct messages.

CVSS v3.1

Score 4.8medium

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected software

Homebrewmore threats →ghsa
openclaw-cli
pkg:brew/openclaw-cli
Affected versions
>=2026.1.29 <2026.2.14

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/04/2026, 13:11:35 UTC

Technical Analysis

The openclaw CLI Slack slash-command handler incorrectly authorized any DM sender to run privileged commands if the Slack DM policy was configured as open (dmPolicy=open). This allowed any Slack user in the workspace who could DM the bot to bypass allowlist and access-group restrictions and execute privileged slash commands. The vulnerability affects openclaw npm package versions >=2026.1.29 and <2026.2.14 with Slack DMs enabled and dmPolicy=open. The issue was fixed by updating the slash-command path to apply the same allowlist/access-group authorization logic for DMs as for other inbound paths. The fix is included in version 2026.2.14.

Potential Impact

Any Slack user in the workspace who can send a direct message to the openclaw bot could execute privileged slash commands without proper authorization, potentially leading to unauthorized actions within the system. The impact is limited to configurations where Slack DMs are enabled with dmPolicy=open.

Mitigation Recommendations

A fix is available in openclaw version 2026.2.14 that corrects the authorization logic for Slack direct messages. Users should upgrade to version 2026.2.14 or later to remediate this vulnerability. Until the patch is applied, avoid using the dmPolicy=open configuration or restrict who can DM the bot.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
BREW-openclaw-cli-CVE-2026-28392
Osv Schema Version
1.7.3
Ecosystems
["Homebrew"]
Cvss Version
3.1

Threat ID: 6ac245cb12601ec6a3167f23

Added to database: 10/04/2026, 12:25:47 UTC

Last enriched: 10/04/2026, 13:11:35 UTC

Last updated: 10/04/2026, 16:08:37 UTC

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses