CVE-2026-73268
MCE cluster-curator-controller allows job-spec injection leading to cluster privilege escalation.
Is CVE-2026-73268 being exploited?
Not confirmed. CVE-2026-73268 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.47% probability of exploitation in the next 30 days.
How severe is CVE-2026-73268?
CVE-2026-73268 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-73268?
Yes. A fix has been recorded for CVE-2026-73268. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-73268 affect?
CVE-2026-73268 affects multicluster engine (MCE) - cluster-curator-controller, Kubernetes clusters using MCE, ClusterCurator resources. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73268?
Restrict ClusterCurator RBAC, block untrusted tenants, audit jobs/secrets, apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Tenant with create/update on ClusterCurator can inject a Job to run as the controller, allowing arbitrary code execution and access to cluster-wide secrets.
Immediate action required