CVE-2026-53818: OpenClaw: MCP loopback auth bypass enables policy evasion
MEDIUMOpenClaw before 2026.4.24 has a missing authorization check (CWE-862) in its MCP loopback feature, allowing any low-privileged local user to invoke owner-only tools and skip before-tool-call security hooks without restriction. The High integrity impact is operationally significant: with AC:L, PR:L, and no user interaction required, anyone with a local shell on a shared OpenClaw deployment can bypass the authorization layer that owner-only policies were explicitly designed to enforce — collapsing the trust boundary between agent privilege tiers. While CISA KEV status is negative and no public exploit exists today, OpenClaw's track record of 155 CVEs in this package indicates systemic security debt that elevates the probability of further abuse. Upgrade to 2026.4.24 immediately per GHSA-rj6p-xmxr-qj4h; if patching is blocked, disable the MCP loopback feature and audit logs for unexpected owner-only tool invocations.
What is the risk?
Medium CVSS (6.6) with a local attack vector limits direct internet-facing exposure, but the High integrity impact combined with trivial exploitation prerequisites (AC:L, PR:L, UI:N) makes this reliably exploitable in any shared or multi-user OpenClaw deployment. In AI agent contexts where owner-only tools gate sensitive operations — file writes, credential-bearing API calls, privileged data access — bypassing these controls effectively nullifies the primary authorization control. The package's history of 155 CVEs indicates systemic authorization debt, raising confidence that this loopback bypass reflects a broader pattern rather than an isolated defect.
How does the attack unfold?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| OpenClaw | pip | — | No patch |
Do you use OpenClaw? You're affected.
How severe is it?
What is the attack surface?
What should I do?
5 steps-
Patch immediately: upgrade OpenClaw to 2026.4.24 or later (see GHSA-rj6p-xmxr-qj4h for patch details).
-
If patching is blocked, disable the MCP loopback feature in OpenClaw configuration or restrict loopback path access to owner-equivalent process contexts only.
-
Enumerate all owner-only tool definitions to assess the blast radius if the bypass has already been exploited.
-
Review OpenClaw access and audit logs for unexpected invocations of owner-only tools from non-owner process contexts.
-
Apply least-privilege to OpenClaw service accounts and restrict local access to systems where OpenClaw runs.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
How many AI incidents are linked? (1)
Source: AI Incident Database (AIID)
Frequently Asked Questions
What is CVE-2026-53818?
OpenClaw before 2026.4.24 has a missing authorization check (CWE-862) in its MCP loopback feature, allowing any low-privileged local user to invoke owner-only tools and skip before-tool-call security hooks without restriction. The High integrity impact is operationally significant: with AC:L, PR:L, and no user interaction required, anyone with a local shell on a shared OpenClaw deployment can bypass the authorization layer that owner-only policies were explicitly designed to enforce — collapsing the trust boundary between agent privilege tiers. While CISA KEV status is negative and no public exploit exists today, OpenClaw's track record of 155 CVEs in this package indicates systemic security debt that elevates the probability of further abuse. Upgrade to 2026.4.24 immediately per GHSA-rj6p-xmxr-qj4h; if patching is blocked, disable the MCP loopback feature and audit logs for unexpected owner-only tool invocations.
Is CVE-2026-53818 actively exploited?
No confirmed active exploitation of CVE-2026-53818 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-53818?
1. Patch immediately: upgrade OpenClaw to 2026.4.24 or later (see GHSA-rj6p-xmxr-qj4h for patch details). 2. If patching is blocked, disable the MCP loopback feature in OpenClaw configuration or restrict loopback path access to owner-equivalent process contexts only. 3. Enumerate all owner-only tool definitions to assess the blast radius if the bypass has already been exploited. 4. Review OpenClaw access and audit logs for unexpected invocations of owner-only tools from non-owner process contexts. 5. Apply least-privilege to OpenClaw service accounts and restrict local access to systems where OpenClaw runs.
What systems are affected by CVE-2026-53818?
This vulnerability affects the following AI/ML architecture patterns: agent frameworks, MCP-based tool ecosystems, multi-user AI agent deployments, agentic automation pipelines.
What is the CVSS score for CVE-2026-53818?
CVE-2026-53818 has a CVSS v3.1 base score of 6.6 (MEDIUM).
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0053 AI Agent Tool Invocation AML.T0084.001 Tool Definitions AML.T0107 Exploitation for Defense Evasion AML.T0112.000 Local AI Agent Compliance Controls Affected
What are the technical details?
Original Advisory
OpenClaw before 2026.4.24 contains an authorization bypass vulnerability in the MCP loopback feature that allows non-owner callers to skip owner-only tool policies and before-tool-call hooks. Attackers can invoke owner-only behavior through the affected loopback path to execute restricted tools when the feature is enabled and reachable.
Exploitation Scenario
A low-privileged local user on a shared AI workstation or server running OpenClaw identifies the MCP loopback endpoint — documented in OpenClaw's own architecture documentation. Using a minimal script or direct API call, they route a tool invocation request through the loopback path, which lacks the authorization check enforcing owner-only restrictions. The before-tool-call hook — intended to validate permissions prior to execution — is also bypassed on this code path. The attacker executes a restricted tool such as a file-write, a credential-retrieving API call, or an agent configuration modification without elevated OS credentials, potentially exfiltrating sensitive data or pivoting to connected systems via the invoked tool's capabilities.
Weaknesses (CWE)
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L References
- github.com/openclaw/openclaw/security/advisories/GHSA-rj6p-xmxr-qj4h vendor-advisory patch
- vulncheck.com/advisories/openclaw-owner-only-tool-policy-bypass-via-mcp-loopback third-party-advisory
Timeline
Related Vulnerabilities
CVE-2026-30741 9.8 OpenClaw: RCE via request-side prompt injection
Same package: openclaw CVE-2026-28451 9.3 OpenClaw: SSRF via Feishu extension exposes internal services
Same package: openclaw GHSA-cwj3-vqpp-pmxr 8.8 openclaw: Model bypasses authz to persist unsafe config
Same package: openclaw CVE-2026-35674 8.8 OpenClaw: scope bypass enables full agent admin takeover
Same package: openclaw CVE-2026-53811 8.8 OpenClaw: privilege escalation via identity spoofing
Same package: openclaw