OpenClaw: Hook-triggered CLI runs could receive owner MCP tool authority
- Product
- OpenClaw
- CVE
- CVE-2026-53814
- Affected
- openclaw < 2026.5.20
- Fixed in
- 2026.5.20
Last verified against sources: October 26, 2026
Am I affected?
OpenClaw: affected openclaw < 2026.5.20. Fixed in 2026.5.20.
- Check your version: run
npm ls openclaw. Versions < 2026.5.20 of openclaw are affected. [1]
What to do now
- Upgrade to the fixed version: run
npm install openclaw@2026.5.20(first patched version 2026.5.20). [1] - Upgrade to
openclaw@2026.5.20or later. [1] - Keep hook tokens secret. [1]
- Restrict network access to hook endpoints. [1]
- Disable hooks when they are not needed. [1]
General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.
What happened
- OpenClaw hook ingress can start automated agent runs using a configured hook token. [1]
- In affected releases, a hook-triggered run could select a bundled CLI backend that received owner-scoped MCP loopback authority instead of a scope appropriate for hook ingress. [1]
- This issue affects the boundary between hook-token automation and owner-only MCP tools. [1]
- It does not affect deployments with hooks disabled. [1]
Impact
What was done
Sources
- GHSA-6fvr-66p3-3qj4 — GitHub Advisory Database
Every statement above was checked against these sources before publishing. Spotted an error? Tell us and we will correct it with a dated note.
Share advisory brief with your team
Copy a plain-text summary for Slack, GitHub issues, or team security channels.
[CVE-2026-53814] OpenClaw: Hook-triggered CLI runs could receive owner MCP tool authority
Product: OpenClaw | Affected: openclaw < 2026.5.20 | Fixed in: 2026.5.20
Summary: OpenClaw hook ingress can start automated agent runs using a configured hook token.
Source & remediation on AgentArmorHQ: https://agentarmorhq.com/incidents/2026/07/cve-2026-53814-openclawCorrections
Report an error or request a correction. We review requests within 5 business days and add a dated correction note.
Discussions for CVE-2026-53814
Ask questions or share configuration tips. Governed by our Community Rules & Terms.
No posts match this filter yet.
Be the first to ask a question or share a working tip.