CVE-2026-71473
Admin-level config injection in search-v2-operator allows container image replacement.
Is CVE-2026-71473 being exploited?
Not confirmed. CVE-2026-71473 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.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-71473?
CVE-2026-71473 is rated High with a CVSS score of 8.5. 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-71473?
Yes. A fix has been recorded for CVE-2026-71473. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-71473 affect?
CVE-2026-71473 affects search-v2-operator, Managed Kubernetes clusters, Container images deployed via operator. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-71473?
Restrict operator admin perms; audit and revert configs; apply vendor patch when available.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Admin with specific cluster permissions can inject configs to replace container images, enabling supply-chain compromise and remote code execution.
Patch when possible