{"id":"CVE-2026-10059","published":"2026-08-05T09:18:13.720","lastModified":"2026-08-06T15:37:22.093","description":"A flaw was found in the Multicluster Engine for Kubernetes ClusterCurator controller. A tenant administrator with namespace-scoped privileges can exploit this vulnerability by creating a namespaced ClusterCurator. This action inadvertently grants the tenant administrator the ability to mint a token for a ServiceAccount with cluster-wide administrative authority. This leads to a privilege escalation, allowing the tenant administrator to gain full control over the cluster.","cvssScore":9.1,"cvssSeverity":"CRITICAL","cvssVector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","cwes":["CWE-266"],"vendors":[],"products":[],"references":[{"url":"https://access.redhat.com/security/cve/CVE-2026-10059","tags":[]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2483187","tags":[]}],"exploitRefs":[],"hasPoc":false,"ai":{"summary":"The flaw allows a tenant administrator with namespace-scoped privileges to exploit a vulnerability in the Multicluster Engine for Kubernetes ClusterCurator controller, leading to privilege escalation and full control over the cluster.","exploitability":"Exploitation requires specific privileges but is considered critical due to the severity of the resulting full cluster control.","blast_radius":"If exploited, this vulnerability could have a significant impact on all resources within the affected Kubernetes cluster.","remediation":"Update the Multicluster Engine for Kubernetes ClusterCurator controller to the latest version that addresses this vulnerability.","tags":["privilege-escalation","kubernetes","cluster-control"],"model":"qwen2.5:7b-instruct","analyzedAt":"2026-08-11T06:45:11.962Z"}}