OpenClaw: Owner-enforced commands could accept wildcard channel senders as command owners
CVE-2026-44991 · GHSA-c28g-vh7m-fm7v · published 2026-04-29 · updated 2026-05-29
- Severity
- Medium
- CVSS score
- 5.3
- Chance of exploitation (EPSS)
- 0.24%
- Fixed in
- 2026.4.21
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
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.
Upgrade openclaw to 2026.4.21 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
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
Upgrade to [email protected] or later. Before upgrading, avoid wildcard/open-DM sender policy on owner-enforced channels, or configure commands.ownerAllowFrom to the intended owner identities.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| openclaw | npm | <= 2026.4.20 | 2026.4.21 |
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
- CriticalOpenClaw: QQBot admin commands could skip DM-only and allowFrom policyopenclaw
- CriticalOpenClaw: Feishu webhook and card-action validation now fail closedopenclaw
- CriticalOpenClaw: Gateway HTTP endpoints re-resolve bearer auth after SecretRef rotationopenclaw
- CriticalOpenClaw: Sandbox escape via TOCTOU race in remote FS bridge readFileopenclaw
- CriticalOpenClaw: Heartbeat context inheritance bypasses sandbox via senderIsOwner escalationopenclaw
- CriticalOpenClaw has a CWD `.env` environment variable injection which bypasses host-env policy and allows config takeoveropenclaw
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.