CVE-2026-10059
Namespace admin can escalate to cluster-admin by minting a ServiceAccount token.
Is CVE-2026-10059 being exploited?
Not confirmed. CVE-2026-10059 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.
How severe is CVE-2026-10059?
CVE-2026-10059 is rated Critical. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-10059?
Yes. A fix has been recorded for CVE-2026-10059. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-10059 affect?
CVE-2026-10059 affects Multicluster Engine for Kubernetes - ClusterCurator controller, Kubernetes clusters using Multicluster Engine (MCE). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-10059?
Restrict namespace admin RBAC, revoke/rotate SA tokens, remove ClusterCurator rights, apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Namespace-scoped tenant admin can create a namespaced ClusterCurator to mint a ServiceAccount token with cluster-admin privileges, enabling full cluster takeover.
Immediate action required