Am I affected by OpenClaw: Hook-triggered CLI runs could receive owner MCP tool authority? What should I do?
OpenClaw hook ingress can start automated agent runs using a configured hook token.
Affected: openclaw < 2026.5.20. Fixed in: 2026.5.20. What should you check, and what should you do about it?
Full incident page with sources: https://agentarmorhq.com/incidents/2026/07/cve-2026-53814-openclaw (opens external site)
1 answer
Am I affected? 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.
What to do now
- Upgrade to the fixed version: run
npm install openclaw@2026.5.20(first patched version 2026.5.20). - Upgrade to
openclaw@2026.5.20or later. - Keep hook tokens secret.
- Restrict network access to hook endpoints.
- Disable hooks when they are not needed.
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.
Sources
- GitHub Advisory Database: https://github.com/advisories/GHSA-6fvr-66p3-3qj4 (opens external site)
Full incident page: https://agentarmorhq.com/incidents/2026/07/cve-2026-53814-openclaw (opens external site)
Did this work for you?- Check your version: run