Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Checkout DevGuardView on GitHub
Search

GHSA-c28g-vh7m-fm7v

MediumCVSS 5.3 / 10
Published Apr 29, 2026·Last modified May 5, 2026
Affected Components(0)

No affected components available

Description

Impact

OpenClaw deployments before 2026.4.21 could treat a non-owner sender as authorized for owner-enforced slash commands when all of the following were true:

  • a channel plugin declared commands.enforceOwnerForCommands: true;
  • the channel accepted wildcard inbound senders with allowFrom: ["*"];
  • no explicit commands.ownerAllowFrom was configured.

In that state, src/auto-reply/command-auth.ts reused the channel inbound wildcard as part of the command-owner decision. A sender who was not the owner could therefore pass the owner-command gate for commands such as /send, /config, or /debug on the affected channel.

The issue is limited to the command-owner authorization axis. It does not by itself grant owner-only tool access, host/sandbox access, or gateway administrator scope.

Affected Packages / Versions

  • Package: openclaw on npm
  • Affected versions: <= 2026.4.20
  • Patched version: 2026.4.21

The latest public release, 2026.4.21, contains the fix.

Patches

The fix requires a concrete owner identity or internal operator-admin scope when a plugin enforces owner-only commands. Wildcard channel allowFrom no longer implies wildcard command ownership.

Fix commits:

  • 2aa93d44a1b2c7058c371f261fda2b5d4de4a882 on main
  • 995febb7b1e811ff6a1df5b18c22de94103f4c9f in the 2026.4.21 release line

Workarounds

Upgrade to openclaw@2026.4.21 or later. Before upgrading, avoid wildcard/open-DM sender policy on owner-enforced channels, or configure commands.ownerAllowFrom to the intended owner identities.

Credits

OpenClaw thanks @zsxsoft for reporting.

Risk Scores
Base Score
5.3

The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability.

Threat Intelligence
1.3

Limited exploitation activity has been observed. Close monitoring and planned remediation are recommended.

EPSS
0.24%

The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Browse More

Medium severity
Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard