Managedcluster-import-controller: csr auto-approver does not validate certificate subject or signername (spoke→hub cluster-admin)
Red Hat multicluster engine for Kubernetes 2.10 · Red Hat multicluster engine for Kubernetes 2.11 · Red Hat multicluster engine for Kubernetes 2.17 · Red Hat multicluster engine for Kubernetes 2.6
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat multicluster engine for Kubernetes 2.10 | — |
|
| Red Hat multicluster engine for Kubernetes 2.11 | — |
|
| Red Hat multicluster engine for Kubernetes 2.17 | — |
|
| Red Hat multicluster engine for Kubernetes 2.6 | — |
|
| Red Hat multicluster engine for Kubernetes 2.8 | — |
|
| Red Hat multicluster engine for Kubernetes 2.9 | — |
|
Original description
A flaw was found in the managedcluster-import-controller. The Certificate Signing Request (CSR) auto-approval logic improperly validates incoming CSRs, specifically by not inspecting the signer name or decoding the PEM-encoded x509 CSR. This vulnerability allows a privileged service account on a spoke cluster to submit a malicious CSR. Successful exploitation can lead to privilege escalation, enabling the attacker to obtain administrative credentials on the hub cluster.
From the CVE record · redhat
References
- access.redhat.com/errata/RHSA-2026:59556
- access.redhat.com/errata/RHSA-2026:59557
- access.redhat.com/errata/RHSA-2026:59558
- access.redhat.com/errata/RHSA-2026:59559
- access.redhat.com/errata/RHSA-2026:59579
- access.redhat.com/errata/RHSA-2026:59593
- access.redhat.com/security/cve/CVE-2026-66795
- bugzilla.redhat.com/show_bug.cgi?id=2507540