# CVE-2026-105312: A Kubernetes tenant with create permission on Console custom resources can set spec.containers.api.spec.image to an arbitrary container image.


- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-5c9w-jj2v-89qh

## What is CVE-2026-105312?

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

### Official description

A Kubernetes tenant with create permission on Console custom resources can set spec.containers.api.spec.image to an arbitrary container image. The operator deploys this image into a pod whose ServiceAccount is bound via ClusterRoleBinding to a ClusterRole granting cluster-wide get/list/watch on all Strimzi CRDs (including KafkaUsers), patch on Kafkas/KafkaRebalances, and cluster-monitoring-view. The attacker's code reads the projected SA token and gains cross-tenant Strimzi control-plane read+write access.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-105312 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105312 is a critical vulnerability in Red Hat StreamsHub Console for Apache Kafka®, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-105312 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-105312/ (Markdown: https://insights.sbomify.com/CVE-2026-105312/index.md)
```

## Sources

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

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