CVE-2026-73269
Local user can escalate namespace access to cluster-admin via cluster-curator-controller.
Is CVE-2026-73269 being exploited?
Not confirmed. CVE-2026-73269 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.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-73269?
CVE-2026-73269 is rated Critical with a CVSS score of 9.9. 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-73269?
Yes. A fix has been recorded for CVE-2026-73269. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-73269 affect?
CVE-2026-73269 affects cluster-curator-controller, Kubernetes clusters running cluster-curator-controller, Operators accepting ClusterCurator resources. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73269?
Restrict/remove controller; block untrusted ClusterCurator creation; apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local unprivileged user can create a ClusterRoleBinding to gain cluster-admin: access secrets, manage/delete hosted clusters and node pools.
Immediate action required