Red Hat Multicluster Engine for Kubernetes ClusterCurator controller privileges management

Summaryinfo

A vulnerability marked as very critical has been reported in Red Hat Multicluster Engine for Kubernetes. Affected by this issue is some unknown functionality of the component ClusterCurator controller. Performing a manipulation results in privileges management. This vulnerability is known as CVE-2026-10059. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability classified as very critical has been found in Red Hat Multicluster Engine for Kubernetes (the affected version is unknown). This affects an unknown code of the component ClusterCurator controller. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

A flaw was found in the Multicluster Engine for Kubernetes ClusterCurator controller. A tenant administrator with namespace-scoped privileges can exploit this vulnerability by creating a namespaced ClusterCurator. This action inadvertently grants the tenant administrator the ability to mint a token for a ServiceAccount with cluster-wide administrative authority. This leads to a privilege escalation, allowing the tenant administrator to gain full control over the cluster.

The advisory is shared at access.redhat.com. This vulnerability is uniquely identified as CVE-2026-10059 since 05/29/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. The exploitation requires an enhanced level of successful authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 08/05/2026). MITRE ATT&CK project uses the attack technique T1068 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-53293). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Virtualization Software

Vendor

• Red Hat

Name

• Multicluster Engine for Kubernetes

License

• open-source

Website

• Vendor: https://www.redhat.com/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion