AI agent vulnerability · OpenClaw

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

mediumCVSS 4.0 6.3 · 3.1 6.5GHSA-qw99-grcx-4pvm

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.

Published Feb 17, 2026 · Updated Mar 6, 2026

Affected packages

openclaw

Ecosystem: npm
Affected: >= 2026.1.14-1, < 2026.2.12
Fixed in: 2026.2.12
Check: npm ls openclaw

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

Credited to qi-scape.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More OpenClaw vulnerabilities

All OpenClaw entries