# CVE-2026-28392: openclaw — Fixed in 2026.2.14

📦 npm

Not in CISA KEV

# CVE-2026-28392 — openclaw

[Fix: openclaw/openclaw@f19eabe](https://github.com/openclaw/openclaw/commit/f19eabee54c49e9a2e264b4965edf28a2f92e657)

CVE-2026-28392 is a CWE-863 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw < 2026.2.14 - Privilege Escalation in Slack Slash Command Handler via Direct Messages

Also known as[GHSA-v773-r54f-q32w](/vulnerability/GHSA-v773-r54f-q32w)

Published

Mar 5, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

## Exploitation Status

### No confirmed exploitation observed yet

-   CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
-   CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-28392.

## EPSS Exploitation Probability

[via FIRST.org ↗](https://www.first.org/epss/)

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs35th percentile — riskier than 35% of all scored CVEsHighest risk

0.00%0.36%0.72%1.07%0.0%0.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/).

## Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

133other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

`openclaw`npm

2.5Mdownloads / week

## Description

### Summary

When Slack DMs are configured with `dmPolicy=open`, the Slack slash-command handler incorrectly treated any DM sender as command-authorized. This allowed any Slack user who could DM the bot to execute privileged slash commands via DM, bypassing intended allowlist/access-group restrictions.

### Affected Packages / Versions

-   Package: `openclaw` (npm)
-   Affected versions: `<= 2026.2.13`
-   Affected configuration: Slack DMs enabled with `channels.slack.dm.policy: open` (aka `dmPolicy=open`)

### Impact

Any Slack user in the workspace who can DM the bot could invoke privileged slash commands via DM.

### Fix

The slash-command path now computes `CommandAuthorized` for DMs using the same allowlist/access-group gating logic as other inbound paths.

Fix commit(s):

-   f19eabee54c49e9a2e264b4965edf28a2f92e657

### Release Process Note

`patched_versions` is set to the planned next release (`2026.2.14`). Once that npm release is published, this advisory should be published.

Thanks @christos-eth for reporting.

## Affected Packages

1 total 1 fixed

Ecosystem

Package

Vulnerable range

Fix

📦npm

`openclaw` 

all versions

2026.2.14`npm install openclaw@2026.2.14`

## Affected Products

1 product · 1 configurations

Application

`openclaw`openclaw

< 2026.2.14

range

## Detection & mitigation playbook

Open-source dependency

1.  ### Detect
    
    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
    
2.  ### Fix
    
    Update openclaw to 2026.2.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-28392 is resolved across your whole dependency graph.
    
3.  ### Workarounds
    
    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
    

## Frequently Asked Questions

\## Summary When Slack DMs are configured with \`dmPolicy=open\`, the Slack slash-command handler incorrectly treated any DM sender as command-authorized. This allowed any Slack user who could DM the bot to execute privileged slash commands via DM, bypassing intended allowlist/access-group restrictions. ## Affected Packages / Versions - Package: \`openclaw\` (npm) - Affected versions: \`<= 2026.2.13\` - Affected configuration: Slack DMs enabled with \`channels.slack.dm.policy: open\` (aka \`dmPolicy=open\`) ## Impact Any Slack user in the workspace who can DM the bot could invoke privileged slash co

O3 Security · Impact-Aware SCA

### Is CVE-2026-28392 in your dependencies?

Find it across npm, including transitive dependencies.

[Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)