Red Hat Multicluster Engine for Kubernetes clusterclaims-controller spec.namespace privileges management

Summaryinfo

A vulnerability identified as critical has been detected in Red Hat Multicluster Engine for Kubernetes. Impacted is an unknown function of the component clusterclaims-controller. The manipulation of the argument spec.namespace leads to privileges management. This vulnerability is referenced as CVE-2026-73267. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in Red Hat Multicluster Engine for Kubernetes (affected version not known) and classified as critical. This issue affects some unknown functionality of the component clusterclaims-controller. The manipulation of the argument spec.namespace with an unknown input leads to a privileges management vulnerability. Using CWE to declare the problem leads to 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. Impacted is availability. The summary by CVE is:

A flaw was found in the clusterclaims-controller component of multicluster engine (MCE). A tenant with standard permissions to create and delete ClusterClaim resources can exploit this by manipulating the `spec.namespace` field. This allows the tenant to specify and delete any ManagedCluster, including the hub's local-cluster or other tenants' clusters, due to a missing ownership check. This vulnerability can lead to a denial of service by enabling unauthorized deletion of ManagedClusters.

The advisory is shared at access.redhat.com. The identification of this vulnerability is CVE-2026-73267 since 08/11/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 08/21/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-63800). 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