Security readout for executives and security teams
Plain-English summary
A namespace administrator could turn limited access into full control of a Kubernetes cluster. By creating a namespaced ClusterCurator, the administrator may obtain a token belonging to a cluster-wide administrative service account. This threatens all workloads, secrets, configurations, and cluster availability—not only resources in the administrator’s namespace.
Executive priority
Treat affected clusters as an urgent remediation priority, especially where namespace administration is delegated to tenants or separate teams. Although exploitation requires existing privileged access and is not reported active, successful abuse crosses a major trust boundary and could compromise the entire cluster. Immediately establish exposure, restrict the triggering permission, and apply applicable Red Hat guidance.
Technical view
A tenant administrator permitted to create a namespaced ClusterCurator can trigger controller behavior that enables minting a token for a cluster-wide administrative ServiceAccount. CVSS 3.1 rates this 9.1: network-accessible, low complexity, high privileges required, no user interaction, changed scope, and high confidentiality, integrity, and availability impact. It maps to CWE-266.
Likely exposure
Exposure requires Red Hat Multicluster Engine, an affected cluster-curator-controller-rhel9 build, and a tenant administrator able to create namespaced ClusterCurator resources. The bundle lists MCE 2.1, 2.6, 2.8, 2.9, and 2.11, but the 2.1 entry’s CPE identifies 2.10; verify this discrepancy with Red Hat.
Exploitation context
The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit. Abuse requires authenticated, namespace-scoped administrative privileges and the ability to create a ClusterCurator. The resulting privilege escalation could provide full cluster control, making delegated or multi-tenant environments the highest concern.
Researcher notes
The bundle does not provide controller implementation details, exact fixed builds, proof-of-concept availability, or observed attacks. Its MCE 2.1 product entry conflicts with a CPE identifying 2.10. The numeric version values appear to be package build identifiers. Confirm product and fixed-build mapping through the applicable Red Hat advisories before making vulnerability-status decisions.
Mitigation direction
- Identify affected cluster-curator-controller-rhel9 deployments and map each to the applicable Red Hat advisory.
- Follow the applicable Red Hat advisory; the bundle does not identify exact fixed package versions.
- Until updated, restrict tenant administrators from creating namespaced ClusterCurator resources wherever operationally feasible.
- Minimize access to the cluster-wide curator ServiceAccount and its token-minting paths.
- Monitor ClusterCurator creation and curator ServiceAccount token activity for unauthorized use.
Validation and detection
- Inventory Multicluster Engine versions and cluster-curator-controller-rhel9 build identifiers across all relevant clusters.
- Compare installed builds with the applicable RHSA; do not rely solely on the inconsistent 2.1/2.10 entry.
- Confirm namespace administrators cannot create ClusterCurator resources unless explicitly required.
- Review audit records for unexpected ClusterCurator creation and curator ServiceAccount token issuance.
- After remediation, verify installed packages against Red Hat guidance and repeat authorization checks.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCredential and access behavior lookup
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.
Open ATT&CK lookupPrivilege behavior lookup
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.
Open ATT&CK lookupContainer behavior lookup
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.
Open ATT&CK lookupCVE-2026-10059 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H2.36redhatVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineredhat
Reported to Red Hat.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineredhat
Made public.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2026:59556CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:59557CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:59558CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:59559CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:59579CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-10059CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2483187CVE reference, redhat · issue-tracking, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Privilege Assignment
Incorrect Privilege Assignment represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.