A vulnerability in the StreamsHub Console for Apache Kafka allows a Console Custom Resource author to inject arbitrary Kafka client configuration. The console‑api AdminClient inherits these properties without filtering security‑sensitive keys, such as config.providers and bootstrap.servers. An attacker who can create or modify a Console CR can point these settings to a rogue Kafka broker and cause the console‑api ServiceAccount token to be sent to the attacker, leading to compromise of the underlying cluster with the permissions of the console‑api ServiceAccount.

Red Hat Streams for Apache Kafka versions 2 and 3 are affected. The vulnerability applies to any deployment that uses the StreamsHub Console operator and allows tenant‑supplied Kafka client properties to be passed to the console‑api AdminClient. No specific sub‑versions are listed; the issue exists in all currently supported releases until a fixed version is released.

The CVSS score of 6.5 indicates a moderate severity. EPSS is not publicly available, and the vulnerability is not listed in the CISA KEV catalog. The attack requires the ability to create, update, or patch Console Custom Resources, which is typically granted to cluster administrators or tenants with privileged access. The broker endpoint can be directed to any arbitrary network address that the console‑api can reach, so the exploit can be performed through normal API calls without additional privileges, but only by users with CR modification rights. The combined factors mean that the risk is moderate but could lead to full cluster compromise if an attacker controls a Console CR.