CVE-2026-53818: OpenClaw · MCP loopback could skip owner-only tool policy for non-owner callers
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 6.6 Medium : upgrade to 2026.4.24 when convenient.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.09% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.4.24
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade openclaw and openclaw-cli to 2026.4.24.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmopenclaw | Affected
| Fixed in
|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available and should be applied when released. Until patched, restrict MCP loopback access to trusted operators only. Additionally, narrow channel and tool allowlists, avoid sharing a Gateway between mutually untrusted users, and disable the affected feature if it is not needed.
Description
A vulnerability in OpenClaw CLI's MCP loopback feature allows non-owner callers to bypass owner-only tool policies and before-tool-call hooks. This issue affects versions from 2026.1.29 up to but not including 2026.4.24. The impact depends on the operator's configuration and whether untrusted inputs can reach the affected loopback path. A patch is available to address this issue. Until patched, restricting MCP loopback access to trusted operators and narrowing allowlists is recommended.