CVE-2026-28395
Openclaw 2026.1.14-1 – 2026.2.12
Raw vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2026-28395 is a medium-severity Binding to an Unrestricted IP Address (CWE-1327) vulnerability in Openclaw Openclaw. Its CVSS base score is 6.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 33th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to CM-6 (Configuration Settings) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-28395 is an improper network binding vulnerability (CWE-1327) affecting OpenClaw versions 2026.1.14-1 prior to 2026.2.12. The issue resides in the relay server of the Chrome extension, which must be installed and enabled. Specifically, the server incorrectly treats wildcard hosts as loopback addresses, causing the HTTP/WS relay server to bind to all network interfaces when a wildcard cdpUrl is configured. This has a CVSS v3.1 base score of 6.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L).
Remote attackers can exploit this vulnerability without privileges by accessing the relay HTTP endpoints from off-host networks. Successful exploitation enables detection of the service's presence and exposed ports, partial information disclosure via leaked service details, denial-of-service attacks against the relay, and brute-force attempts on the relay token header.
Advisories and patch notes, including GitHub security advisory GHSA-qw99-grcx-4pvm and commits 8d75a496bf5aaab1755c56cf48502d967c75a1d0 and a1e89afcc19efd641c02b24d66d689f181ae2b5c, recommend upgrading to OpenClaw version 2026.2.12 or later, where the binding logic is fixed to properly restrict wildcard configurations to loopback interfaces only. The VulnCheck advisory further details the unintended public binding via wildcard cdpUrl.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-9895
Vulnerability Data
OpenClaw version 2026.1.14-1 prior to 2026.2.12 contains an improper network binding vulnerability in the Chrome extension (must be installed and enabled) relay server that treats wildcard hosts as loopback addresses, allowing the relay HTTP/WS server to bind to all interfaces…
more
when a wildcard cdpUrl is configured. Remote attackers can access relay HTTP endpoints off-host to leak service presence and port information, or conduct denial-of-service and brute-force attacks against the relay token header.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Establishes the most restrictive configuration settings, which would require binding only to specific addresses rather than 0.0.0.0.
Enforces approved information flow policies that would disallow unrestricted remote bindings.
Enforces least functionality by prohibiting unnecessary network exposure such as unrestricted listening addresses.
Requires control of communications at external and key internal interfaces, preventing binding that accepts traffic from any source.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Configuration management enforces restricted bind addresses, covering the weakness completely but only one aspect of overall hardening.
Network protection controls directly prevent exposure via unrestricted binds while fixing the weakness addresses only one vector of unauthorized access.
Documenting authorized network flows informs correct bind decisions and reduces the chance of 0.0.0.0 usage.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security of network services includes hardening service bindings to prevent exposure on all interfaces.
Secure architecture principles discourage exposing services on all interfaces, though the control is broader than this single weakness.
Network security controls directly require restricting listening interfaces to specific addresses rather than 0.0.0.0.
Network segregation can limit the blast radius of an unrestricted binding but does not prevent the binding itself.
Secure coding guidance can catch hard-coded 0.0.0.0 bindings during development but is not the primary mitigation.