Allows tenant-deployed container to run in operator with ClusterRoleBinding-granted cluster-wide Strimzi privileges, enabling cross-tenant takeover of Kafka resources in widely used Kubernetes/Strimzi environments.
CVE-2026-105312
K8s operator image exploit lets tenant seize Strimzi/Kafka control
Is CVE-2026-105312 being exploited?
Not confirmed. CVE-2026-105312 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.
How severe is CVE-2026-105312?
CVE-2026-105312 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-105312?
Yes. A fix has been recorded for CVE-2026-105312. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-105312 affect?
CVE-2026-105312 affects Strimzi (Kafka Operator), Kubernetes clusters (Console CRs), Red Hat OpenShift (operator deployments). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-105312?
Apply vendor patch, revoke excess ClusterRoleBindings, block untrusted image deployments
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker can run arbitrary image in operator pod, read SA token, gain cross-tenant Strimzi CRD read/write and control Kafka users (remote code execution/privilege escalation).
Immediate action required
- affected>= 0.2.0 and < 0.12.10
- affected>= 0.13.0 and < 0.14.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.