GitHub Advisoryadvisory · npm

GHSA-qw99-grcx-4pvm OpenClaw's Chrome extension relay binds publicly due to wildcard treated as loopback

MEDIUM Published 2026-02-17 Modified 2026-03-06 Official page ↗
Aliases
CVE-2026-28395
Ecosystem
npm
Packages
openclaw
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
Weaknesses
CWE-1327, CWE-284
Reviewed
2026-02-17

Affected packages

• npm openclaw: >= 2026.1.14-1, < 2026.2.12 → fixed in 2026.2.12

Description

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` (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.

Related

Alias · CVE (1)

  • CVE-2026-28395 OpenClaw version 2026.1.14-1 prior to 2026.2.12 contains an improper network binding vulnerability in the Chrome extension (must be… vulnerability

Weakness · CWE (2)

  • CWE-1327 Binding to an Unrestricted IP Address weakness
  • CWE-284 Improper Access Control weakness

References