https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 23:22:24 +0000 https://vulnerability.circl.lu/vuln/cve-2026-53814 <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw before 2026.5.20 contains a privilege escalation vulnerability where hook-triggered agent runs incorrectly receive owner-scoped MCP loopback authority instead of hook-appropriate scope. Attackers with a valid hook token can exploit the /hooks/agent endpoint to cause spawned CLI runtimes to access or invoke owner-only MCP tools, potentially executing privileged actions like persistent cron state modifications.</p> <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw before 2026.5.20 contains a privilege escalation vulnerability where hook-triggered agent runs incorrectly receive owner-scoped MCP loopback authority instead of hook-appropriate scope. Attackers with a valid hook token can exploit the /hooks/agent endpoint to cause spawned CLI runtimes to access or invoke owner-only MCP tools, potentially executing privileged actions like persistent cron state modifications.</p> https://vulnerability.circl.lu/vuln/cve-2026-53814 https://vulnerability.circl.lu/vuln/ghsa-6fvr-66p3-3qj4 <p><strong>Affected:</strong> npm: openclaw</p> <p>### Summary</p> <p>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.</p> <p>This issue affects the boundary between hook-token automation and owner-only MCP tools. It does not affect deployments with hooks disabled.</p> <p>### Affected configurations</p> <p>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.</p> <p>### Impact</p> <p>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.</p> <p>### Patched Versions</p> <p>The first stable patched version is `2026.5.20`.</p> <p>Fixed in the `2026.5.20` stable release.</p> <p>### Mitigations</p> <p>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.</p> <p><strong>Affected:</strong> npm: openclaw</p> <p>### Summary</p> <p>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.</p> <p>This issue affects the boundary between hook-token automation and owner-only MCP tools. It does not affect deployments with hooks disabled.</p> <p>### Affected configurations</p> <p>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.</p> <p>### Impact</p> <p>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.</p> <p>### Patched Versions</p> <p>The first stable patched version is `2026.5.20`.</p> <p>Fixed in the `2026.5.20` stable release.</p> <p>### Mitigations</p> <p>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.</p> https://vulnerability.circl.lu/vuln/ghsa-6fvr-66p3-3qj4