GHSA-qw99-grcx-4pvm

OpenClaw's Chrome extension relay binds publicly due to wildcard treated as loopback

Source: GitHub Advisory Database (reviewed) Moderate CVE-2026-28395

Packages

Ecosystem	Package	Affected	Fixed in
npm	openclaw	>= 2026.1.14-1, < 2026.2.12	2026.2.12

Details

As written in the advisory (Markdown source, shown as plain text).

## Summary The Chrome extension relay (`ensureChromeExtensionRelayServer`) previously treated wildcard hosts (`0.0.0.0` / `::`) as loopback, which could make it bind the relay HTTP/WS server to all interfaces when a wildcard `cdpUrl` was passed. ## Impact If configured with a wildcard `cdpUrl`, relay HTTP endpoints could become reachable off-host, leaking service presence/port and enabling DoS/brute-force traffic against the relay token header. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected: `>= 2026.1.14-1 < 2026.2.12` ## Fixed Versions - Patched: `>= 2026.2.12` (released 2026-02-13) ## Fix Commit(s) - 8d75a496bf5aaab1755c56cf48502d967c75a1d0 ## Notes - Earlier hardening for `/json*` auth and `/cdp` token checks landed in: - a1e89afcc19efd641c02b24d66d689f181ae2b5c Thanks @qi-scape for reporting.

References

External links from the advisory. They lead to third-party sites.