A tenant with create permission on the StreamsHub Console custom resource can specify an arbitrary container image for the console operator. The operator deploys that image into a pod whose ServiceAccount is bound via a ClusterRoleBinding to a ClusterRole that grants cluster‑wide read, listing, and patch abilities on all Strimzi custom resources, including KafkaUsers and Kafkas. Inside the container the attacker can read the projected ServiceAccount token and use it to obtain cross‑tenant control‑plane read and write access to Strimzi objects, effectively escalating privileges from the tenant level to the entire cluster. This flaw is a classic example of improper privilege management, represented by CWE‑269. The consequence is a high‑impact breach that allows an attacker to modify or delete Kafka resources and potentially disrupt cluster operations.

Red Hat StreamsHub Console for Apache Kafka, Red Hat Streams for Apache Kafka versions 2 and 3 are affected. The vulnerability is present in the amq_streams 2 and 3 product families, as indexed by the corresponding CPEs.

The CVSS score for this issue is 9.9, indicating critical severity. The EPSS score is not available, but the lack of listing in the CISA KEV catalog does not diminish its risk; the flaw can be exploited by any tenant user who has the ability to create or modify Console custom resources. The attack vector is internal to the cluster environment, requiring only Kubernetes tenant privileges. An attacker who supplies a malicious Docker image can instantiate a pod that exfiltrates the ServiceAccount token and manipulates Strimzi control‑plane objects cluster‑wide, leading to potential data loss, denial of service, or full cluster compromise.