A flaw was found in the Submariner operator. The Submariner Custom Resource (CR), used for configuring network connectivity, stores the IPsec pre-shared key (PSK) in an unencrypted format. This key, which is critical for securing communication between Kubernetes clusters, can be accessed by unauthorized parties. Such access enables an attacker to passively decrypt network traffic flowing between any two clusters in the mesh, resulting in sensitive information disclosure.
CVE-2026-66781
Score 6.5 from GitHub Security Advisory published 2026-08-18. a secondary CVSS source baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(high)
- EG Risk
- 29(Track)EG Risk 29/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 0%
- KEV
- Not listed
Published
August 18, 2026
Last Modified
August 20, 2026
Advisory Details (2)
Auto-updated Aug 18, 20262507526 – (CVE-2026-66781) CVE-2026-66781 submariner-operator: submariner-operator: IPsec PSK stored cleartext in Submariner CR spec
https://bugzilla.redhat.com/show_bug.cgi?id=2507526CVE-2026-66781 - 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-66781Vendor Advisories for CVE-2026-66781(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 12× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 13:56 UTCGHSA enrichment
- 2026-08-19 20:56 UTCEG score recompute
- 2026-08-19 20:56 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 20:23 UTCEG score recompute
- 2026-08-18 20:23 UTCGHSA enrichment
- 2026-08-18 19:29 UTCEG score recompute
- 2026-08-18 19:29 UTCGHSA enrichment
- 2026-08-18 17:21 UTCEG score recompute
- 2026-08-18 17:16 UTCEG score recompute
- 2026-08-18 17:14 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-312
Frequently asked(5)
What is CVE-2026-66781?
When was CVE-2026-66781 disclosed?
Is CVE-2026-66781 actively exploited?
What is the CVSS score of CVE-2026-66781?
How do I remediate CVE-2026-66781?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-66781
Is Your Infrastructure Affected by CVE-2026-66781?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.