CVE-2026-66418

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

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

Score 9.3 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-30. The CNA's CVSS baseline 9.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this weekElevated
9.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.3Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

OpenClaw Dashboard v3.0.0 contains a stored cross-site scripting vulnerability that allows unauthenticated remote attackers to inject arbitrary HTML and script payloads by submitting a crafted username in a failed login POST request, which is recorded verbatim in the audit log. When an administrator opens the notification panel, the unescaped log entry is rendered via innerHTML with a permissive Content-Security-Policy allowing inline event handlers, enabling the attacker-supplied payload to execute in the administrator's session and interact with authenticated endpoints including agent instruction file editing and configuration changes.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
58
EG Risk 58/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)
Severity93% × 45%
Impact severity (EG Severity): CVSS 9.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.6%
EPSS %ILE
49th
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.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.

EG Severity
9.3 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-19). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

July 30, 2026

Last Modified

September 24, 2026

Advisory Details (3)

Auto-updated Oct 3, 2026
No fix on record yet.
Web page

OpenClaw Dashboard v3.0.0 Stored XSS via Failed Login Username Field | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openclaw-dashboard-stored-xss-via-failed-login-username-field
Web page

GitHub - theopaid/CVE-2026-66418-OpenClaw-Dashboard-v3.0.0-Stored-XSS-via-Failed-Login-Username-Field: Security Advisory: Unauthenticated Stored Cross-Site Scripting Leading To Administrator Account Takeover (openclaw-dashboard) · GitHub

https://github.com/theopaid/Unauthenticated-Stored-Cross-Site-Scripting-Leading-To-Administrator-Account-Takeover
Web page

GitHub - tugcantopaloglu/openclaw-dashboard: 🔐 Secure, real-time monitoring dashboard for OpenClaw AI agents. Auth, TOTP MFA, cost tracking, live feed, memory browser and more. · GitHub

https://github.com/tugcantopaloglu/openclaw-dashboard

Vendor Advisories for CVE-2026-66418(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 89× 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 100 of 413 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. None are among the latest 100 rows. The 313 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-66418?
CVE-2026-66418 is a critical-severity vulnerability; its CVE record was published on July 30, 2026. OpenClaw Dashboard v3.0.0 contains a stored cross-site scripting vulnerability that allows unauthenticated remote attackers to inject arbitrary HTML and script payloads by submitting a crafted username in a failed login POST request, which is recorded verbatim in the audit log. When an…
When was CVE-2026-66418 made public?
CVE-2026-66418 was made public on July 30, 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 July 30, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-66418 actively exploited?
CVE-2026-66418 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-66418?
CVE-2026-66418 has a CVSS base score of 9.3 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-66418?
No fix for CVE-2026-66418 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-66418 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-66418

Explore →

Is Your Infrastructure Affected by CVE-2026-66418?

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