CVE-2026-44118: OpenClaw · MCP loopback owner context is derived from server-issued bearer tokens
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 8.5 High : upgrade to 2026.4.22 soon.
Data as of 17 Nov 2026, 20:25 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.5 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 7.8 |
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.4.22
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 6 May 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 17 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.4.22.
Affected software
| Product | 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
Upgrade openclaw-cli to version 2026.4.22 or later, which contains the official fix. The fix removes the spoofable sender-owner header and enforces authentication based on distinct bearer tokens for owner and non-owner contexts.
Description
A vulnerability in openclaw-cli versions up to 2026.4.21 allows a non-owner loopback client to spoof owner context metadata via request headers. This could enable unauthorized access to owner-gated operations. The issue is fixed in version 2026.4.22 by issuing separate bearer tokens for owner and non-owner contexts and no longer trusting the spoofable sender-owner header.
References
- github.com/openclaw/openclaw/security/advisories/GHSA-r6xh-pqhr-v4xh (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-44118 (opens in a new tab)
- github.com/openclaw/openclaw/commit/3cb1a56bfc9579a0f2336f9cfa12a8a744332a19 (opens in a new tab)
- github.com/openclaw/openclaw (opens in a new tab)
- vulncheck.com/advisories/openclaw-owner-context-spoofing-via-bearer-token-header (opens in a new tab)