High [CVE-2026-105311] Streams for Apache Kafka Console: cross-namespace KafkaUser Secret exfiltration via confused deputy
This high-severity Red Hat Linux advisory covers CVE-2026-105311; related products: streams for Apache Kafka 2, streams for Apache Kafka 3.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
Streams for Apache Kafka Console: cross-namespace KafkaUser Secret exfiltration via confused deputy. Red Hat rates this important (CVSS 7.7).
Weakness: CWE-441.
Affected products named by the advisory: streams for Apache Kafka 2; streams for Apache Kafka 3.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 12 hours ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 12 hours ago·verify at source
Mitigation checklist
- 1. Restrict Console CR RBAC — remove create/update verbs on consoles.console.streamshub.github.com from tenant-facing roles. Only trusted cluster administrators should manage Console CRs. 2. Audit existing Console CRs — review all Console CRs for kafkaUser.namespace fields pointing outside the CR's own namespace. 3. Network policy (defense-in-depth) — apply NetworkPolicy to restrict operator pod egress. --- 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 enforce strict same-namespace boundary validation on KafkaUser credentials namespace references in Console Operator custom resources to prevent cross-namespace Secret reads: upgrade to the fixed Console Operator builds, which enforce an assertNamespaceAllowed() guard with a same-namespace default check when reading KafkaUser namespace configuration, closing all 2 injection vectors (Console custom resource namespace manipulation, cross-namespace Secret reference). Until patched, this is a concern on Kubernetes clusters running Console Operator where non-admin users have create or update permissions on Console custom resources, so Remove create and update permissions on Console custom resources from tenant roles and audit existing custom resources for kafkaUser.namespace values pointing outside their own namespace. As a compensating measure, Configure Kubernetes API server audit logging to record Console custom resource modifications and cross-namespace Secret read operations performed by the operator service account. These controls limit blast radius and contain exploitation, but they do not fix the underlying confused deputy cross-namespace access defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-711 Admission Controller Policy Enforcement (OPA/Gatekeeper/Kyverno) (high)
Official advisory · high-confidence parse· fetched 12 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.