CVE-2026-66788

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-20. A secondary CVSS source baseline 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-63535 (ENISA EUVD) · GHSA-264j-8377-4hmm (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in Lighthouse. A remote attacker, by compromising a spoke cluster, can exploit a vulnerability where the destination namespace for resource injection is derived from an attacker-controlled label or annotation on the broker object. This allows the attacker to inject unauthorized EndpointSlices and ServiceImports into any namespace on peer clusters, including critical system namespaces like kube-system and openshift-*. This could lead to privilege escalation or other forms of system compromise within the cluster.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
45
EG Risk 45/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
51st
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.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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; Track* at high (mission-essential systems).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, 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; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (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.

The score's inputs: 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

August 20, 2026

Last Modified

October 19, 2026

Advisory Details (4)

Auto-updated Oct 26, 2026
Patch available. Sources: redhat.
Red HatMentions a patch (unverified)

2507533 – (CVE-2026-66788) CVE-2026-66788 lighthouse: lighthouse: arbitrary namespace injection via attacker-controlled broker label

https://bugzilla.redhat.com/show_bug.cgi?id=2507533
Red HatMentions a patch (unverified)

CVE-2026-66788 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-66788
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:85227
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:63016

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhacm2/submariner-rhel9-operator:17906709122026-10-19redhat
redhatrhacm2/submariner-rhel9-operator:17880734812026-09-03redhat

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.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 27× in last 7d / 163× 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 599 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 499 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-66788?
CVE-2026-66788 is a critical-severity vulnerability; its CVE record was published on August 20, 2026. A flaw was found in Lighthouse. A remote attacker, by compromising a spoke cluster, can exploit a vulnerability where the destination namespace for resource injection is derived from an attacker-controlled label or annotation on the broker object. This allows the attacker to inject unauthorized…
When was CVE-2026-66788 made public?
CVE-2026-66788 was made public on August 20, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on August 20, 2026. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-66788 actively exploited?
CVE-2026-66788 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-66788?
CVE-2026-66788 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-66788?
A fix for CVE-2026-66788 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-66788 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-66788?

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