No advisories yet.
Solution
No solution given by the vendor.
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.
Tue, 18 Aug 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 18 Aug 2026 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Submariner-operator: submariner-operator: broker api bearer token stored cleartext in cr spec | |
| First Time appeared |
Redhat
Redhat acm |
|
| Weaknesses | CWE-312 | |
| CPEs | cpe:/a:redhat:acm:2 | |
| Vendors & Products |
Redhat
Redhat acm |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2026-08-18T19:53:15.244Z
Reserved: 2026-07-27T17:51:24.885Z
Link: CVE-2026-66782
Updated: 2026-08-18T19:47:53.599Z
Status : Received
Published: 2026-08-18T17:17:00.710
Modified: 2026-08-18T20:17:22.450
Link: CVE-2026-66782
No data.
OpenCVE Enrichment
Updated: 2026-08-18T19:00:12Z