{"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 escalate their permissions by creating a namespaced ClusterCurator, leading to full cluster control.","exploitability":"Exploitation requires a tenant administrator with specific privileges and knowledge of the ClusterCurator feature. The vulnerability is relatively hard to exploit due to the required access level.","blast_radius":"If exploited, the tenant administrator gains full control over the cluster, potentially leading to widespread damage or data loss.","remediation":"Disable the ClusterCurator feature or restrict access to it strictly to users with the necessary permissions.","detection":"No reliable host or network indicator is derivable from the published description.","tags":["auth-bypass","priv-escalation","kubernetes"],"model":"qwen2.5:7b-instruct","analyzedAt":"2026-09-29T09:10:04.879Z"}}