# CVE-2026-66780: Submariner-operator: broker serviceaccount secret (token + ca) logged in full at trace verbosity

> Excessive permissions in the submariner-operator allow compromised clusters to modify network configurations and intercept inter-cluster traffic.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-3xmh-phwc-5f4g

## What is CVE-2026-66780?

CVE-2026-66780 is a medium-severity missing authorization vulnerability in Red Hat Advanced Cluster Management for Kubernetes 2, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in the submariner-operator component. The `submariner-k8s-broker-cluster` Role, which is assigned to joined clusters, possesses excessive permissions. This allows a compromised cluster to alter network configurations, specifically by overwriting other clusters' endpoint information. Consequently, an attacker can redirect inter-cluster tunnel traffic, enabling a Man-in-the-Middle (MITM) attack across the entire cluster mesh.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2026-66780?


## How do I fix CVE-2026-66780?

No fix has been published for CVE-2026-66780 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-66780 being exploited?

There is no known exploitation of CVE-2026-66780 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-66780 and fix it if it is affected.

What it is: CVE-2026-66780 is a medium-severity missing authorization vulnerability in Red Hat Advanced Cluster Management for Kubernetes 2, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-66780 in the wild and no public exploit code.

Affected product: Red Hat Advanced Cluster Management for Kubernetes 2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-66780/ (Markdown: https://insights.sbomify.com/CVE-2026-66780/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-66780
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-66780
- OSV: https://osv.dev/vulnerability/CVE-2026-66780

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-66780/
Summaries are generated and may contain mistakes; the official description above is the record.