The submariner‑operator component contains a role misconfiguration that grants every joined cluster excessive permissions over the broker namespace. An attacker who compromises a spoke cluster can overwrite the endpoint data of other clusters, redirecting inter‑cluster tunnel traffic and enabling a man‑in‑the‑middle attack across the entire mesh. This flaw directly compromises network confidentiality and integrity for all participants in the cluster network.

The vulnerability applies to Red Hat Advanced Cluster Management for Kubernetes version 2 through its submariner-operator deployment. No specific patch versions are listed, and the issue is tied to the Role assignment created by the submariner‑k8s‑broker‑cluster component in the broker namespace.

The reported CVSS score of 6.5 indicates a medium‑severity rating. The EPSS score of 0.00303 (less than 1%) suggests a very low exploitation probability, but the lack of a KEV listing does not diminish the risk; the remediation remains urgent. Attackers would need to compromise a cluster that has joined the broker, which is a plausible scenario in environments using the operator. Because the malicious actor can modify critical network configuration objects, the practical impact is substantial, warranting immediate mitigation.