Skip to main content
VulnerabilityPublished Updated

CVE-2026-28395: Openclaw cli · OpenClaw's Chrome extension relay binds publicly due to wildcard treated as loopback

Affects openclaw-cliSource GCVE Database

0
Compare

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

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
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:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threatsAffected
  • >=2026.1.29 <2026.2.12
Fixed in
  • 2026.2.12

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

Community reviews

Loading reviews…