CVE-2026-28395

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.5% (39th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 6.5 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-02-17) is not newer than that change (2026-06-17), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-9895 (ENISA EUVD) · GHSA-qw99-grcx-4pvm (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 5, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Chrome extension relay binds publicly due to wildcard treated as loopback · Advisory · openclaw/openclaw · GitHub

https://github.com/openclaw/openclaw/security/advisories/GHSA-qw99-grcx-4pvm
GitHub commit

commit a1e89afcc19e (openclaw/openclaw)

Fix landed in openclaw/openclaw commit a1e89afcc19e — awaiting tagged release

https://github.com/openclaw/openclaw/commit/a1e89afcc19efd641c02b24d66d689f181ae2b5c
GitHub commit

commit 8d75a496bf5a (openclaw/openclaw)

Fix landed in openclaw/openclaw commit 8d75a496bf5a — awaiting tagged release

https://github.com/openclaw/openclaw/commit/8d75a496bf5aaab1755c56cf48502d967c75a1d0

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmopenclaw @ 2026.2.12 (fixes >= 2026.1.14-1, < 2026.2.12)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
openclaw—
  • 2026.1.14-1 up to 2026.2.12: fixed in 2026.2.12
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× in last 7d / 57× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 232 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 137 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 20:47 UTCEG score recompute
  2. 2026-11-01 20:47 UTCGHSA enrichmentGHSA-qw99-grcx-4pvm · GitHub severity MODERATE · GitHub CVSS 6.5
  3. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  4. 2026-11-01 07:55 UTCGHSA enrichmentGHSA-qw99-grcx-4pvm · GitHub severity MODERATE · GitHub CVSS 6.5
  5. 2026-11-01 07:55 UTCEG score recompute
  6. 2026-10-31 18:31 UTCEG score recompute
  7. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  9. 2026-10-30 16:08 UTCEG score recompute
  10. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  11. 2026-10-29 13:52 UTCEG score recompute
  12. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  13. 2026-10-28 11:36 UTCEG score recompute
  14. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  15. 2026-10-27 09:02 UTCEG score recompute
  16. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  17. 2026-10-26 05:35 UTCEG score recompute
  18. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  19. 2026-10-25 14:38 UTCEG score recompute
  20. 2026-10-25 03:16 UTCEG score recompute
  21. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  22. 2026-10-24 01:01 UTCEG score recompute
  23. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  24. 2026-10-22 22:45 UTCEG score recompute
  25. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.8% · 54th percentile
Show 70 more
  1. 2026-10-21 20:28 UTCEG score recompute
  2. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  3. 2026-10-20 18:12 UTCEG score recompute
  4. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  5. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  6. 2026-10-19 15:53 UTCEG score recompute
  7. 2026-10-18 03:50 UTCEG score recompute
  8. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  9. 2026-10-17 11:20 UTCEG score recompute
  10. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  11. 2026-10-16 09:03 UTCEG score recompute
  12. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  13. 2026-10-15 06:46 UTCEG score recompute
  14. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  15. 2026-10-14 02:28 UTCEG score recompute
  16. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  17. 2026-10-12 22:43 UTCEG score recompute
  18. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  19. 2026-10-12 16:16 UTCEG score recompute
  20. 2026-10-11 19:59 UTCEG score recompute
  21. 2026-10-11 17:12 UTCEG score recompute
  22. 2026-10-11 15:06 UTCOSV refresh
  23. 2026-10-11 14:42 UTCEG score recompute
  24. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  25. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  26. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  27. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  28. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  29. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  30. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  31. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  32. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  33. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  34. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  35. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  36. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  37. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  38. 2026-09-22 02:45 UTCOSV refresh
  39. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  40. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  41. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  42. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  43. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  44. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  45. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  46. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  47. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  48. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  49. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  50. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  51. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  52. 2026-09-03 00:00 UTCOSV refresh
  53. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  54. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  55. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  56. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  57. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  58. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  59. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  60. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  61. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  62. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  63. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  64. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  65. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  66. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  67. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  68. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  69. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  70. 2026-08-16 12:25 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-28395?
CVE-2026-28395 is a critical-severity vulnerability; its CVE record was published on March 5, 2026. 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 when a wildcard…
When was CVE-2026-28395 made public?
CVE-2026-28395 was made public on February 14, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on March 5, 2026. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-28395 actively exploited?
CVE-2026-28395 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-28395?
CVE-2026-28395 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-28395?
A fix for CVE-2026-28395 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-28395

Explore →

Is Your Infrastructure Affected by CVE-2026-28395?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.