CVE-2026-10059: Cluster-curator-controller: cluster-curator-controller: namespace admin can escalate to cluster-wide curator authority via clustercurator serviceaccount token
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.
Security readout for executives and security teams
Plain-English summary
A namespace administrator can abuse ClusterCurator creation to obtain credentials carrying cluster-wide administrative authority. Successful exploitation could give a tenant full control of the Kubernetes cluster, affecting data confidentiality, system integrity, and availability.
Executive priority
Treat as an immediate priority wherever namespace administration is delegated to tenants. A compromised or malicious tenant administrator could cross the isolation boundary and take over the cluster. Prioritize exposure review, permission restriction, investigation, and vendor-directed remediation.
Technical view
CVE-2026-10059 is a privilege-escalation flaw in Red Hat Multicluster Engine’s ClusterCurator controller. Creating a namespaced ClusterCurator can allow a namespace-scoped administrator to mint a token for a ServiceAccount with cluster-wide authority. It is classified as CWE-266 and scored CVSS 3.1 9.1.
Likely exposure
Exposure requires Red Hat Multicluster Engine for Kubernetes and a tenant administrator able to create namespaced ClusterCurator resources. The bundle identifies the cluster-curator-controller-rhel9 package as affected but provides no affected or fixed version boundaries, so installations require vendor-guided verification.
Exploitation context
The attack is network-accessible, low complexity, requires high namespace-scoped privileges, and needs no user interaction. The CVSS scope change reflects escalation beyond the tenant namespace. The bundle marks KEV false and provides no evidence of active exploitation.
Researcher notes
The described security boundary failure is clear, but public details in the supplied bundle are incomplete. No affected-version range, fixed release, named patch, vendor mitigation, proof of concept, or exploitation evidence is provided. Validation should remain non-invasive and focus on RBAC, resource history, and token audit records.
Mitigation direction
Check Red Hat guidance for affected versions, patches, upgrades, and supported mitigations.
Restrict tenant permission to create ClusterCurator resources until vendor remediation is confirmed.
Review and minimize access to the cluster-wide curator ServiceAccount and its token-creation paths.
Rotate or invalidate suspect credentials after investigating possible unauthorized token issuance.
Validation and detection
Inventory Multicluster Engine installations and identify installed cluster-curator-controller-rhel9 versions.
Identify tenants and roles permitted to create namespaced ClusterCurator resources.
Review existing ClusterCurator objects for unexpected tenant-created resources.
Audit ServiceAccount token issuance and cluster-wide actions for suspicious curator identity use.
Confirm remediation status against Red Hat guidance because fixed versions are absent from the bundle.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-266: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
5Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-266 · source CWE mapping
Incorrect Privilege Assignment
Incorrect Privilege Assignment represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.