Description
A flaw was found in the cluster-curator-controller component. A local user, by creating a ClusterCurator resource with a specific naming convention, can trigger the creation of a cluster-scoped ClusterRoleBinding. This allows the user to escalate their privileges from namespace-local access to cluster-wide control. This privilege escalation grants broad permissions, including the ability to access and manipulate secrets, manage cluster actions, and delete hosted clusters or node pools.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Red Hat multicluster engine for Kubernetes 2.10
Default version status: affected
1787201612 to < *unaffected
Red Hat multicluster engine for Kubernetes 2.11
Default version status: affected
1787238383 to < *unaffected
Red Hat multicluster engine for Kubernetes 2.17
Default version status: affected
1786750700 to < *unaffected
Red Hat multicluster engine for Kubernetes 2.6
Default version status: affected
1787264185 to < *unaffected
Red Hat multicluster engine for Kubernetes 2.8
Default version status: affected
1787259011 to < *unaffected
Red Hat multicluster engine for Kubernetes 2.9
Default version status: affected
1787201646 to < *unaffected
References
- https://access.redhat.com/errata/RHSA-2026:59556 ↗
- https://access.redhat.com/errata/RHSA-2026:59557 ↗
- https://access.redhat.com/errata/RHSA-2026:59558 ↗
- https://access.redhat.com/errata/RHSA-2026:59559 ↗
- https://access.redhat.com/errata/RHSA-2026:59579 ↗
- https://access.redhat.com/errata/RHSA-2026:59593 ↗
- https://access.redhat.com/security/cve/CVE-2026-73269 ↗
- https://bugzilla.redhat.com/show_bug.cgi?id=2514220 ↗