CVE-2026-66786

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-70247 (ENISA EUVD) · GHSA-f6r4-g4jr-h7f2 (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
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: 1.4%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in submariner. In cert-auth mode, the connection configuration is built using free-form strings from the Custom Resource Definition (CRD) without proper validation. A malicious cluster can exploit this by publishing a CableName that includes newlines and ipsec.conf directives. This allows an attacker to inject arbitrary configuration parameters or execute commands through leftupdown hooks, leading to remote code execution as root on the gateway node.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/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.
Exploitation1.4% × 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
1.4%
EPSS %ILE
72nd
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.GitHub Security Advisory CVSS
EG Likelihood
1.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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

September 2, 2026

Last Modified

October 19, 2026

Advisory Details (3)

Auto-updated Sep 15, 2026
Patch available. Sources: redhat.
Red Hat

2507531 – (CVE-2026-66786) CVE-2026-66786 submariner: submariner: ipsec.conf stanza injection via remote-supplied CableName and Subnets

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

CVE-2026-66786 - 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-66786
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:63016

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhacm2/submariner-route-agent-rhel9:17906702542026-10-19redhat
redhatrhacm2/submariner-route-agent-rhel9:17880439702026-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(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 94× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 613 rows 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 513 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-66786?
CVE-2026-66786 is a critical-severity vulnerability; its CVE record was published on September 2, 2026. A flaw was found in submariner. In cert-auth mode, the connection configuration is built using free-form strings from the Custom Resource Definition (CRD) without proper validation. A malicious cluster can exploit this by publishing a CableName that includes newlines and ipsec.conf directives. This…
When was CVE-2026-66786 made public?
CVE-2026-66786 was made public on August 21, 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 September 2, 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-66786 actively exploited?
CVE-2026-66786 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (72nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-66786?
CVE-2026-66786 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-66786?
A fix for CVE-2026-66786 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-66786 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-66786?

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