CVE-2026-66782Submariner-operator: operator clusterrole grants cluster-wide create/update on all configmaps
- 5.8MediumCVSS base score
- 0.38%Exploitation in 30 daysEPSS · top 68% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
A flaw was found in the Submariner operator. This vulnerability allows for the exposure of a long-lived broker service account (SA) bearer token within the Submariner Custom Resource (CR) specification. An attacker with access to the cluster's etcd database or through `kubectl get` commands could obtain this token. The possession of this token grants full control over the mesh network, enabling unauthorized management of network resources such as endpoints and secrets.
Timeline
ID reserved
By redhat
- 22 days later
· 22 days later
Published
- 2 months later
· 2 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| redhatCNA (assigner) | 3.1 | Medium5.8 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N |
| NVDNVD · Awaiting Analysis | 3.1 | Medium5.8 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N |
- EPSS (exploitation in 30 days)
- 0.38% · top 68% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.8.
Affected products
Red Hat · Red Hat Advanced Cluster Management for Kubernetes 2.16
- unaffected 1790670243 – < *
Red Hat · Red Hat Advanced Cluster Management for Kubernetes 2.16
- unaffected 1790670912 – < *
Red Hat · Red Hat Advanced Cluster Management for Kubernetes 2.17
- unaffected 1788105072 – < *
Red Hat · Red Hat Advanced Cluster Management for Kubernetes 2.17
- unaffected 1788073481 – < *
Red Hat · Red Hat Advanced Cluster Management for Kubernetes 2
All versions: affected
Red Hat · Red Hat Advanced Cluster Management for Kubernetes 2
All versions: affected
What to do
Workaround: To mitigate this issue, ensure that access to Submariner Custom Resources (CRs) is strictly controlled. Implement Kubernetes Role-Based Access Control (RBAC) policies to limit read access to Submariner CRs only to authorized administrators and components that explicitly require it. This reduces the risk of unauthorized disclosure of the broker Service Account bearer token, which may be stored in cleartext within the CR's specification field. Review existing RBAC configurations to ensure least privilege is applied to resources containing sensitive information.
References
References4
- RHSA-2026:63016 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- RHSA-2026:85227 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-66782 (opens in a new tab)vdb-entryx_refsource_REDHAT
- RHBZ#2507527 (opens in a new tab)issue-trackingx_refsource_REDHAT
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-61066 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-66782)Record last updated .