Restricted tool execution via MCP loopback policy bypass
Published Jun 11, 2026 · Updated Jun 11, 2026
Authorization bypass in OpenClaw before 2026.4.24 allows local users to execute restricted tools through the MCP loopback path. The loopback handler omits owner-only tool policy enforcement and before-tool-call hooks for non-owner callers. Exploitation requires low-privileged local access plus an enabled and reachable MCP loopback feature; resulting tool actions depend on operator configuration.
Summary
What happened
Authorization bypass in OpenClaw before 2026.4.24 allows local users to execute restricted tools through the MCP loopback path. The loopback handler omits owner-only tool policy enforcement and before-tool-call hooks for non-owner callers. Exploitation requires low-privileged local access plus an enabled and reachable MCP loopback feature; resulting tool actions depend on operator configuration.
The record
- CVE
- CVE-2026-53818
- Published
- Jun 11, 2026
- Updated
- Jun 11, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-862, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 11, 2026CVE publishedPublication date reported by the CVE source.
- Jun 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2026.4.24
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo