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.
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/cdptoken checks landed in:- a1e89afcc19efd641c02b24d66d689f181ae2b5c
Thanks @qi-scape for reporting.
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.
CVE-2026-28395 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.12); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-28395? CVE-2026-28395 is a medium-severity security vulnerability in openclaw (npm), affecting versions >= 2026.1.14-1, < 2026.2.12. It is fixed in 2026.2.12.
- How severe is CVE-2026-28395? CVE-2026-28395 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of openclaw are affected by CVE-2026-28395? openclaw (npm) versions >= 2026.1.14-1, < 2026.2.12 is affected.
- Is there a fix for CVE-2026-28395? Yes. CVE-2026-28395 is fixed in 2026.2.12. Upgrade to this version or later.
- Is CVE-2026-28395 exploitable, and should I be worried? Whether CVE-2026-28395 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-28395 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-28395? Upgrade
openclawto 2026.2.12 or later.