cve.bz

CVE-2026-105311 red hat streamshub console for apache kafka®: Confused Deputy

7.7 highEPSS 0.3%

High (7.7) in red hat streamshub console for apache kafka®. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
The StreamsHub Console operator acts as a confused deputy: a Kubernetes tenant with permission to create a Console custom resource can set spec.kafkaClusters[].credentials.kafkaUser.namespace to any namespace. The operator, running with cluster-wide Secrets RBAC, reads the victim-namespace KafkaUser Secret (SASL credentials or TLS private keys) and writes the plaintext material into a Secret in the attacker's namespace. No same-namespace check or allowlist exists anywhere in the code path.

Severity

CVSS 3.1

7.7 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 23rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-441 Unintended Proxy or Intermediary (Confused Deputy)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-105311 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105311?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105311?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-105311 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • red hat:streamshub console for apache kafka®

Versions

From the CNA's record in the CVE List.

ProductAffected
Red Hat StreamsHub Console for Apache Kafka®from 0.2.0 before 0.12.10
Red Hat StreamsHub Console for Apache Kafka®from 0.13.0 before 0.14.2

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is evaluated as an Important severity flaw because an authenticated tenant can break multi-tenant boundary isolation by leveraging the operator to expose confidential cluster secrets from outside their own project. In Red Hat AMQ Streams deployments on OpenShift, the Streams for Apache Kafka Console component operates with broad cluster-level permissions to manage resources across projects. Although exploitation requires existing privileges to deploy or modify Console resources, the resulting loss of confidentiality spans all namespaces in shared clusters, justifying the Important rating over Moderate.

Red Hat's mitigation

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)

ProductPackageStateAdvisory
streams for Apache Kafka 2console-operatorAffected
streams for Apache Kafka 3console-operatorAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-105311.

Attack patterns (CAPEC)

  • CAPEC-219 XML Routing Detour Attacks Likelihood: High · Severity: Medium
  • CAPEC-465 Transparent Proxy Abuse Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON