CVE-2026-28395: Openclaw cli · OpenClaw's Chrome extension relay binds publicly due to wildcard treated as loopback
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 6.5 Medium : upgrade to 2026.2.12 when convenient.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.2.12
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 16 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.2.12.
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
A patch is available and should be applied by upgrading to openclaw version 2026.2.12 or later. This update corrects the binding behavior to prevent the relay server from binding publicly when a wildcard cdpUrl is used.
Description
A vulnerability in the OpenClaw CLI Chrome extension relay caused the relay HTTP/WS server to bind publicly when configured with a wildcard cdpUrl. This occurred because wildcard hosts were incorrectly treated as loopback addresses. The issue could expose relay endpoints off-host, leaking service presence and enabling denial-of-service or brute-force attacks against the relay token header. The flaw affects versions from 2026.1.14-1 up to but not including 2026.2.12 and was fixed in version 2026.2.12.
References
- github.com/openclaw/openclaw/security/advisories/GHSA-qw99-grcx-4pvm (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-28395 (opens in a new tab)
- github.com/openclaw/openclaw/commit/8d75a496bf5aaab1755c56cf48502d967c75a1d0 (opens in a new tab)
- github.com/openclaw/openclaw/commit/a1e89afcc19efd641c02b24d66d689f181ae2b5c (opens in a new tab)
- github.com/openclaw/openclaw (opens in a new tab)
- github.com/openclaw/openclaw/releases/tag/v2026.2.12 (opens in a new tab)
- vulncheck.com/advisories/openclaw-unintended-public-binding-of-chrome-extension-relay-via-wildcard-cdpurl (opens in a new tab)