Skip to content
VulniPulse
Highest advisory severityMedium 1 vendor · 1 advisory

CVE-2026-66782

CVE-2026-66782: 1 tracked advisory record across Red Hat. Compare vendor sources and published fix guidance.

Compare the source-linked records below. Ratings and product/version details belong to each advisory; they are not a single CVE-wide score or proof that every listed product is affected. How VulniPulse collects and checks evidence.

Vendor advisory comparison

Red Hat

1 advisory
  • Advisory severityMedium5.8

    Medium [CVE-2026-66782] Operator ClusterRole grants cluster-wide create/update on all ConfigMaps

    CVE-2026-66782Source published Source updated

    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…

    Affected products in this advisory
    • Red Hat Advanced Cluster Management for Kubernetes 2.17
    Source-reported affected versions
    Affected-version details not available in this record.
    Source-reported fixed versions
    • rhacm2/subctl-rhel9:1788105072
    • rhacm2/submariner-rhel9-operator:1788073481
    • RHSA-2026:63016
    Mitigation guidance
    • 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.

Android app · Google Play

Monitor future Red Hat 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.

Matching phone alertsOptional email delivery