CVE-2026-105312
Console-operator: streams for apache kafka console: tenant-controlled container image on clusterrole-bound pod enables namespace-to-cluster privilege escalation
- Critical 9.9
Description
A Kubernetes tenant with create permission on Console custom resources can set spec.containers.api.spec.image to an arbitrary container image. The operator deploys this image into a pod whose ServiceAccount is bound via ClusterRoleBinding to a ClusterRole granting cluster-wide get/list/watch on all Strimzi CRDs (including KafkaUsers), patch on Kafkas/KafkaRebalances, and cluster-monitoring-view. The attacker's code reads the projected SA token and gains cross-tenant Strimzi control-plane read+write access.
Key facts
- Published
- 20 Oct 2026
- Last changed
- 3 Nov 2026
- Assigned by
- redhat
- EPSS
- 0.336% likely to be exploited in the next 30 days, higher than 27.458% of CVEs (scores for 18 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: no; Technical impact: total
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 9.9CVSS 3.1, Criticalfrom the CNA (redhat)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
What to do
- 1. Restrict Console CR RBAC — remove create/update/patch verbs on consoles.console.streamshub.github.com from tenant-level Roles. Only cluster administrators should manage Console CRs. 2. Deploy admission webhook — use OPA/Gatekeeper or Kyverno policy to validate spec.containers.api.spec.image against a trusted registry allowlist. 3. Apply network policies — restrict console-api pod egress to only required endpoints. 4. Single-tenant deployment — deploy the Console operator where only trusted administrators manage Console CRs. --- CME Mitigation Guidance (2026-10-20) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to eliminate unvalidated container image deployment in the Console operator by enforcing image allowlists or removing tenant image override capabilities: upgrade to the fixed Console Operator builds, which requires image allowlist validation or removal of tenant image override capability to prevent deploying unvalidated images into pods bound to cluster-wide Strimzi CRD permissions, closing all 2 injection vectors (arbitrary container image injection via spec.containers.api.spec.image, ServiceAccount token exfiltration from privileged pod). UntilCNA workaround statement
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
CNA context is abbreviated; consult the original record for the complete statements.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Red Hat | StreamsHub Console for Apache Kafka® |
|
| Red Hat | streams for Apache Kafka 2 |
|
| Red Hat | streams for Apache Kafka 3 |
|
Timeline
- 4 Aug 2026 Reported to Red Hat.
- 20 Oct 2026 Made public.
- 20 Oct 2026 Published