CVE-2026-71470
Privileged CR editor can replace image or inject secrets, risking full cluster compromise
Is CVE-2026-71470 being exploited?
Not confirmed. CVE-2026-71470 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.42% probability of exploitation in the next 30 days.
How severe is CVE-2026-71470?
CVE-2026-71470 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-71470?
Yes. A fix has been recorded for CVE-2026-71470. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-71470 affect?
CVE-2026-71470 affects search-v2-operator (Kubernetes operator), Kubernetes clusters, Containers using operator-managed Search CR, ServiceAccounts with impersonation permissions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-71470?
Restrict CR edit and impersonation RBAC, audit operator configs, and apply vendor patch when released
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
CR editors can mount secrets or replace container images to escalate privileges and fully compromise Kubernetes clusters via ServiceAccount impersonation.
Immediate action required