CVE-2026-105311
Received Received - Intake

StreamsHub Console Operator Accesses Arbitrary KafkaUser Secrets

Publication date: 2026-10-20

Last updated on: 2026-10-20

Assigner: redhat-SADP

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-20
Last Modified
2026-10-20
Generated
2026-10-20
AI Q&A
2026-10-20
EPSS Evaluated
N/A
NVD
CVE-2026-105311
EUVD
EUVD-2026-104963

Affected Vendors & Products

Showing 4 associated CPEs
Vendor Product Version / Range
Red Hat StreamsHub Console for Apache Kafka® 0.2.0
Red Hat StreamsHub Console for Apache Kafka® 0.13.0
Red Hat streams for Apache Kafka 2 *
Red Hat streams for Apache Kafka 3 *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-441 The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-105311 is a confused deputy vulnerability in the StreamsHub Console operator for Kubernetes. A tenant with permission to create a Console custom resource can set the KafkaUser namespace to any namespace. The operator, running with cluster-wide Secrets RBAC permissions, reads KafkaUser Secrets (containing SASL credentials or TLS private keys) from the victim's namespace and writes them into a Secret in the attacker's namespace. No same-namespace validation exists.

Detection Guidance

Check for Console custom resources with cross-namespace KafkaUser references by inspecting YAML manifests or using kubectl get console -A. Look for spec.kafkaClusters[].credentials.kafkaUser.namespace set to a namespace other than the Console CR's namespace.

Impact Analysis

An attacker with tenant permissions can exfiltrate sensitive Kafka credentials (SASL or TLS private keys) from other namespaces to their own. This allows unauthorized access to Kafka clusters, potentially leading to data breaches, message interception, or further lateral movement within the Kubernetes cluster.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating confidentiality requirements in GDPR and HIPAA. Organizations using this software may face compliance violations, data breach notifications, and potential fines due to exposure of personal or health information.

Mitigation Strategies

Remove create/update permissions for tenant-facing roles on Console CRs. Audit existing Console CRs for cross-namespace KafkaUser references and remove them. Apply NetworkPolicy to restrict operator pod egress as a defense-in-depth measure.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-105311. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart