The OpenClaw Chrome extension relay server incorrectly treats wildcard host entries as loopback addresses, causing the HTTP/WS server to bind to all network interfaces when a wildcard cdpUrl is configured. This improper network binding allows remote attackers to reach the relay endpoints from outside the host, potentially leaking the presence of the service and exposing port information. The vulnerability also enables denial‑of‑service and brute‑force attacks against the authentication token header. The weakness is a classic example of CWE‑1327, improper network bound address handling. Only Chrome extensions that are installed and enabled are at risk; the flaw is not tied to arbitrary code execution but to unauthorized exposure of an internal service.

Affected is the OpenClaw application (OpenClaw:OpenClaw). All releases from 2026.1.14‑1 up to, but not including, 2026.2.12 are vulnerable. Users running any of these versions with the Chrome extension enabled are at risk.

The CVSS score of 6.3 classifies the vulnerability as moderate severity, and the EPSS score of less than 1% indicates a very low exploitation probability at the time of this analysis. The exploit requires the victim to have the Chrome extension installed and enabled, and an attacker must target the host that has bound the relay to all interfaces. Because the exploit does not require local code execution, the attack vector is remote network access. Although the likelihood is low, the impact could be significant for exposed services, especially if an attacker can use brute‑force token attacks to compromise the relay. As of now the vulnerability is not listed in the CISA KEV catalog, but any organization that exposes the relay can inadvertently allow external discovery. Given the moderate CVSS score and low EPSS, patching should be prioritized but urgent attribution is not mandatory for all environments.