# CVE-2026-105311: Console-operator: streams for apache kafka console: cross-namespace kafkauser secret exfiltration via confused deputy


- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-h4vv-pfp4-5x34

## What is CVE-2026-105311?

CVE-2026-105311 is a high-severity vulnerability in Red Hat StreamsHub Console for Apache Kafka®, published on 20 Oct 2026. 

### Official 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.

Weakness: CWE-441 (Unintended Proxy or Intermediary)

## Which versions are affected by CVE-2026-105311?


## How do I fix CVE-2026-105311?

No fix has been published for CVE-2026-105311 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-105311 being exploited?

There is no known exploitation of CVE-2026-105311 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105311 and fix it if it is affected.

What it is: CVE-2026-105311 is a high-severity vulnerability in Red Hat StreamsHub Console for Apache Kafka®, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-105311 in the wild and no public exploit code.

Affected product: Red Hat StreamsHub Console for Apache Kafka®. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-105311/ (Markdown: https://insights.sbomify.com/CVE-2026-105311/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-105311
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-105311
- OSV: https://osv.dev/vulnerability/CVE-2026-105311

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-105311/
Summaries are generated and may contain mistakes; the official description above is the record.