CVE-2026-70495
Kubernetes operator service account allows cluster-admin impersonation.
Is CVE-2026-70495 being exploited?
Not confirmed. CVE-2026-70495 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.11% probability of exploitation in the next 30 days.
How severe is CVE-2026-70495?
CVE-2026-70495 is rated High with a CVSS score of 8.8. 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-70495?
Yes. A fix has been recorded for CVE-2026-70495. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-70495 affect?
CVE-2026-70495 affects search-v2-operator, Kubernetes clusters running the operator, Pods using search-serviceaccount. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-70495?
Remove/restrict cluster-level bindings, revoke ClusterRoleBindings, isolate affected pods, rotate creds; apply patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Compromise of any pod using the search-serviceaccount enables impersonation and escalation to system:masters, allowing full cluster takeover.
Immediate action required