OpenClaw's authorization mismatch allowed write-scope agent runs to reach owner-only tools
GHSA-jr6x-2q95-fh2g · published 2026-03-02
- Severity
- High
- CVSS score
- 8.7
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 2026.3.1
On affected deployments, write-scoped callers could perform control-plane actions beyond intended write scope.
Upgrade openclaw to 2026.3.1 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.
Owner-only gating is now enforced consistently for owner-only tool surfaces during agent execution, and tool scope classification was tightened to remove the privilege mismatch.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| openclaw | npm | < 2026.3.1 | 2026.3.1 |
- 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.