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
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| Red Hat | multicluster engine for Kubernetes 2.10 | — | — |
| Red Hat | multicluster engine for Kubernetes 2.11 | — | — |
| Red Hat | multicluster engine for Kubernetes 2.17 | — | — |
| Red Hat | multicluster engine for Kubernetes 2.6 | — | — |
| Red Hat | multicluster engine for Kubernetes 2.8 | — | — |
| Red Hat | multicluster engine for Kubernetes 2.9 | — | — |
References
- RHSA-2026:59556 vendor-advisory
- RHSA-2026:59557 vendor-advisory
- RHSA-2026:59558 vendor-advisory
- RHSA-2026:59559 vendor-advisory
- RHSA-2026:59579 vendor-advisory
- RHSA-2026:59593 vendor-advisory
- https://access.redhat.com/security/cve/CVE-2026-73269 vdb-entry
- RHBZ#2514220 issue-tracking