---
id: "CVE-2026-105311"
kind: "vulnerability"
aliases: ["CVE-2026-105311"]
title: "StreamsHub Console operator leaks Kafka user secrets across Kubernetes namespaces"
severity: "high"
cvss: 7.7
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: [{"name": "streamshub-console", "fixed": ["0.12.10", "0.14.2"], "affected": ">= 0.2.0, < 0.12.10; >= 0.13.0, < 0.14.2", "ecosystem": "vendor"}]
ecosystems: []
tags: ["console-operator", "infrastructure", "kafka", "kubernetes", "multi-tenant", "streamshub", "strimzi"]
not_affected_if: ["console-cr-admin-only", "console-creation-restricted", "single-tenant", "single-tenant-cluster", "version-0.14.2+"]
published_at: "2026-10-20T12:17:28+00:00"
first_seen_at: "2026-10-23T21:57:20+00:00"
updated_at: "2026-10-25T03:31:33+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-105311", "first_seen_at": "2026-10-23T21:57:20+00:00"}, {"source": "analyst", "url": null, "first_seen_at": "2026-10-25T03:31:33+00:00"}]
---

# StreamsHub Console operator leaks Kafka user secrets across Kubernetes namespaces

The StreamsHub Console operator copies KafkaUser Secrets (SASL credentials or TLS private keys) from any namespace into a Secret the requesting tenant can read, because it lacks a same-namespace check. A Kubernetes tenant allowed to create a Console resource can read Kafka credentials belonging to other tenants.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:streamshub-console affected >= 0.2.0, < 0.12.10; >= 0.13.0, < 0.14.2 fixed 0.12.10, 0.14.2

## How to check

Run: kubectl get deploy -A -o wide | grep -i console, and check the operator image tag; versions >= 0.2.0 < 0.12.10 and >= 0.13.0 < 0.14.2 are affected. Run: kubectl get console -A -o yaml and look for spec.kafkaClusters[].credentials.kafkaUser.namespace values that differ from the CR's own namespace. Check who can create Console CRs: kubectl auth can-i create consoles.console.streamshub.github.com --as <tenant-user> -n <ns>. Rotate any KafkaUser credentials that a cross-namespace CR could have copied.

## Fix

Upgrade the StreamsHub Console operator to 0.14.2 (0.13.x/0.14.x) or 0.12.10 (0.12.x line). From 0.14.2 the operator checks that the Console service account may read the referenced KafkaUser Secret (SubjectAccessReview), so grant it a Role/RoleBinding on any KafkaUser Secrets it must use. Until upgraded: remove create/update on consoles.console.streamshub.github.com from tenant roles, and audit Console CRs.

## Timeline

- 2026-10-23T21:57:20+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-105311
- 2026-10-25T03:31:33+00:00 analyst — Fix in StreamsHub Console 0.14.2 (release notes + PR #3040) and 0.12.10 for the 0.12 line (0.12.10 from CNA ranges only, release page not read). Red Hat's CME mitigation text is AI-generated, so I did not verify it. No exploitation or PoC found.

## Documents

- [advisory] Red Hat CVE-2026-105311 https://access.redhat.com/security/cve/cve-2026-105311
- [fix] streamshub/console #3040 Require Console service account access to KafkaUser secret https://github.com/streamshub/console/pull/3040
- [fix] streamshub/console releases (0.14.2) https://github.com/streamshub/console/releases

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_