Bug 2565162 (CVE-2026-120472)

Summary: CVE-2026-120472 hive: hive: ClusterClaim controller grants cross-tenant hive-claim-owner RBAC via user-controlled spec.namespace
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: crizzo, efried, gparvin, jbalunas, lberk, mold, rhaigner, security-response-team, sumehta, tsze
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in OpenShift Hive. The ClusterClaim controller assigns hive-claim-owner RBAC based on a user-controlled ClusterClaim.spec.namespace and only verifies ClusterPoolRef.ClaimName. A tenant can point a same-named claim at another tenant's ClusterDeployment and obtain get access to that cluster's admin kubeconfig and admin password secrets.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Deadline: 2026-12-17   

Description OSIDB Bzimport 2026-11-02 13:01:12 UTC
A flaw was found in the OpenShift Hive ClusterClaim controller (github.com/openshift/hive). ClusterClaim.spec.namespace is an optional, user-settable field with no immutability rule and no hiveadmission validating webhook. On the assignment path, Reconcile loads the ClusterDeployment named by claim.Spec.Namespace and only checks that ClusterDeployment.Spec.ClusterPoolRef.ClaimName equals the claim name before calling reconcileForExistingAssignment and createRBAC. That path never verifies that ClusterPoolRef.Namespace matches the claim namespace, although the cleanup path in the same controller does perform that check.

A tenant who can create ClusterClaims in their own namespace can create a claim whose name matches a victim tenant claim and whose spec.namespace points at the victim cluster namespace, with spec.subjects set to themselves. Hive then creates the hive-claim-owner Role and RoleBinding in the victim ClusterDeployment namespace, granting the attacker get access to that cluster's admin kubeconfig and admin password secrets (cluster-admin on the managed OpenShift cluster).

The clusterpool controller does not clear a pre-set spec.namespace that points at a foreign ClusterDeployment, so the claim controller acts on the attacker-set value. A nil dereference also occurs if a claim is pointed at a ClusterDeployment with no ClusterPoolRef.

Affected code: pkg/controller/clusterclaim/clusterclaim_controller.go on master and mce-2.6, mce-2.7, and mce-2.8 branches. Confirmed with unit-test reproduction using Hive test builders: an attacker claim in another namespace, named identically to a victim claim with spec.namespace pointing at the victim cluster, is granted hive-claim-owner before a namespace-equality fix and denied after.

This is distinct from MCE stolostron/clusterclaims-controller issues such as CVE-2026-73267 (ManagedCluster deletion) and CVE-2026-73266 (label confused deputy).