How severe is GHSA-v773-r54f-q32w?

GHSA-v773-r54f-q32w has a CVSS score of 4.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-v773-r54f-q32w?

GHSA-v773-r54f-q32w affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-v773-r54f-q32w?

Update openclaw to 2026.2.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v773-r54f-q32w is resolved across your whole dependency graph.

How do I detect GHSA-v773-r54f-q32w in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-v773-r54f-q32w if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-v773-r54f-q32w?

O3 pinpoints whether GHSA-v773-r54f-q32w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-v773-r54f-q32w actively exploited in the wild?

No public exploit code has been indexed for GHSA-v773-r54f-q32w yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-v773-r54f-q32w?

GHSA-v773-r54f-q32w has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 26th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-v773-r54f-q32w published, and has it been updated?

GHSA-v773-r54f-q32w was published on February 18, 2026 and was last updated on March 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-v773-r54f-q32w

MEDIUM

OpenClaw Slack: dmPolicy=open allowed any DM sender to run privileged slash commands

Also known asCVE-2026-28392

Published

Feb 18, 2026

Updated

Mar 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk26th percentile+0.30%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

📦openclaw

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

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

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openclaw to 2026.2.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v773-r54f-q32w is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-v773-r54f-q32w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-v773-r54f-q32w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 GHSA-v773-r54f-q32w in your dependencies?

O3 detects GHSA-v773-r54f-q32w across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works