High

OpenClaw: Hook-triggered CLI runs could receive owner MCP tool authority

  • Disclosed: 02.07.2026
  • Updated: 11.10.2026 10:22

Summary

OpenClaw hook ingress can start automated agent runs using a configured hook token. 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.

This issue affects the boundary between hook-token automation and owner-only MCP tools. It does not affect deployments with hooks disabled.

Affected configurations

This affects deployments where hooks are enabled, /hooks/agent is reachable with a valid hook token, and a bundled CLI backend can be selected for the hook-triggered run.

Impact

A caller with the hook token could cause the spawned CLI runtime to see or call MCP tools that should have been owner-only. The practical impact depends on which MCP tools are available; the reported proof used persistent cron state as a representative owner-only action.

Patched Versions

The first stable patched version is 2026.5.20.

Fixed in the 2026.5.20 stable release.

Mitigations

Upgrade to openclaw@2026.5.20 or later. Keep hook tokens secret, restrict network access to hook endpoints, and disable hooks when they are not needed.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package openclaw < 2026.5.20 2026.5.20

References

CVSS score 8.4/10
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
Weakness (CWE)
CWE-200, CWE-266, CWE-284
Platform
npm
Package
openclaw
Disclosed
02.07.2026
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-6fvr-66p3-3qj4 - CC BY 4.0

Vulnerability history: openclaw

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (588) in the archive
Total entries
588
First → latest
02.2026 07.2026
Without a fix
9
Exploited in attacks
0

Severity breakdown

  • Critical 20
  • High 215
  • Medium 299
  • Low 54

Disclosures per year

  1. 2026: 588
Severity:
  1. High · 8.8 CVE-2026-53811 < 2026.5.7 2026.5.7
  2. High · 8.8 CVE-2026-53806 < 2026.5.12 2026.5.12
  3. High · 7.8 CVE-2026-53813 < 2026.4.25 2026.4.25
  4. High · 7.5 CVE-2026-53834 < 2026.4.27 2026.4.27
  5. Critical CVE-2026-34507 < 2026.4.29 2026.4.29
  6. High CVE-2026-53823 < 2026.5.3 2026.5.3
  7. OpenClaw: Hook-triggered CLI runs could receive owner MCP tool authority this entry
    High · 8.4 CVE-2026-53814 < 2026.5.20 2026.5.20
  8. High · 6.5 CVE-2026-53815 < 2026.5.19 2026.5.19
  9. High · 8.1 CVE-2026-53849 < 2026.5.7 2026.5.7
  10. High · 8.1 CVE-2026-53857 < 2026.5.3 2026.5.3
  11. High · 8.1 CVE-2026-53866 < 2026.5.12 2026.5.12
  12. High · 8.1 CVE-2026-53864 < 2026.5.26 2026.5.26
Show more (20) Showing 40 of 235

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.