Bug 2514218 (CVE-2026-73267) - CVE-2026-73267 clusterclaims-controller: clusterclaims-controller: ManagedCluster deletion keyed solely on ClusterClaim.Spec.Namespace with no ownership check
Summary: CVE-2026-73267 clusterclaims-controller: clusterclaims-controller: ManagedClu...
Keywords:
Status: NEW
Alias: CVE-2026-73267
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-11 17:18 UTC by OSIDB Bzimport
Modified: 2026-08-21 02:42 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-11 17:18:36 UTC 
A flaw was found in the clusterclaims-controller component of multicluster engine (MCE). The controller's deleteResources() function uses the tenant-controlled ClusterClaim.Spec.Namespace field to identify the target ManagedCluster for deletion without any ownership or owner-reference check. A tenant with standard create and delete permissions on ClusterClaim resources can set spec.namespace to the name of any ManagedCluster (including the hub's local-cluster or other tenants' clusters), and upon deleting the ClusterClaim, the controller deletes the targeted ManagedCluster. No admission webhook or CRD CEL validation constrains the spec.namespace field.

Upstream repo: https://github.com/stolostron/clusterclaims-controller
Audited commit: 89615dc8ce2de4aac192bf0289ab1a345947f28c
Jira tracker: ACM-38721
Note You need to log in before you can comment on or make changes to this bug.