Medium [CVE-2026-66782] Operator ClusterRole grants cluster-wide create/update on all ConfigMaps
This medium-severity Red Hat Linux advisory covers CVE-2026-66782 affecting Red Hat Advanced Cluster Management for Kubernetes 2.17.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
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.
This configuration exposes the token to cluster administrators or any entity with read access to the CR, potentially granting full mesh control over the Submariner network. This risk is heightened by the token's long-lived nature and its exposure through standard Kubernetes tools like `kubectl get` and `must-gather`.
Red Hat severity: Important — CVSS 5.8 (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N). Weakness: CWE-269.
Affected Red Hat products: Red Hat Advanced Cluster Management for Kubernetes 2.17; Red Hat Advanced Cluster Management for Kubernetes 2. Red Hat fixing advisory: RHSA-2026:63016.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 23 days ago·verify at source
- rhacm2/subctl-rhel9:1788105072
- rhacm2/submariner-rhel9-operator:1788073481
- RHSA-2026:63016
Official advisory · high-confidence parse· fetched 23 days ago·verify at source
Mitigation checklist
- 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.
Official advisory · high-confidence parse· fetched 23 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.