CVE-2026-66795
CSR auto-approval flaw lets spoke SA obtain hub cluster admin credentials.
Is CVE-2026-66795 being exploited?
Not confirmed. CVE-2026-66795 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.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-66795?
CVE-2026-66795 is rated Critical with a CVSS score of 9.1. 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-66795?
Yes. A fix has been recorded for CVE-2026-66795. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-66795 affect?
CVE-2026-66795 affects managedcluster-import-controller, Open Cluster Management (OCM), Kubernetes hub/spoke clusters. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-66795?
Restrict/rotate spoke SAs, disable CSR auto-approval, audit creds, apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Privilege escalation: privileged service account on a spoke can submit crafted CSR to obtain hub admin credentials and full cluster takeover.
Immediate action required