External risk intelligence

Kubernetes Strimzi CRD Image Control Compromise Leads to Cross-Tenant Access

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-105312

This vulnerability requires an existing authenticated tenant with specific permissions within a Kubernetes cluster to exploit a misconfiguration in how container images are deployed by an operator. It is not an internet-facing service or edge component, but rather an internal control plane issue requiring prior authenticated access to the cluster environment.

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability exists in Kubernetes environments utilizing Strimzi, allowing a tenant with specific permissions to deploy arbitrary container images. This could grant them unauthorized cross-tenant control-plane access to sensitive Strimzi resources. The primary concern is confirming if this specific misconfiguration is present and exposed within your environment.

Tenant can run any code in the cluster.
Impacts cross-tenant data and control.
Confirm relevance and exposure to Strimzi.

Attack Path

How an attacker could exploit the issue

A Kubernetes tenant with create permissions on Console custom resources can leverage this vulnerability to gain unauthorized access to sensitive information and control over Strimzi resources. By specifying an arbitrary container image in a Console custom resource, the attacker can trick the operator into deploying this image within a pod. This pod's ServiceAccount is then bound to a ClusterRole that grants extensive read and write permissions across Strimzi custom resources, effectively allowing the attacker to manipulate the Strimzi control plane and potentially other cluster resources.

Authenticated tenant with create permissions.
Deploying arbitrary container image via Console CR.
Unauthorized Strimzi control-plane access.

Live Threat

Current exploitation, exposure, and threat context

A Kubernetes tenant with create permissions on Console custom resources could deploy an arbitrary container image. This image could leverage a service account token to gain cross-tenant access to Strimzi's control plane, allowing for unauthorized read and write operations on Strimzi resources.

Strimzi control plane access.
Arbitrary container image deployment.
Unauthorized resource modifications.

Operational Fix

Recommended remediation, mitigation, and detection steps

A Kubernetes administrator or platform team is likely responsible for managing the operator and its configurations, while application owners may need to be involved to understand the impact on their deployed workloads. The first practical step is to identify all Kubernetes clusters where the affected operator is deployed, confirm if tenant users have `create` permissions on `Console` custom resources, and assess the business criticality of the Strimzi custom resources.

Platform team owns operator deployment and configuration.
Verify tenant `create` permissions on `Console` CRs.
Plan remediation based on Strimzi CR criticality.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is Strimzi and how does it relate to Kubernetes?

Strimzi is an open-source project that simplifies running Apache Kafka on Kubernetes. It uses custom resource definitions to manage Kafka clusters, topics, and users natively within the Kubernetes control plane. In this CVE, the operator that manages these resources is being manipulated, allowing unauthorized access to the Kafka management layer.

What does CWE-269 mean for CVE-2026-105312?

CWE-269 is Improper Privilege Management. In the context of this vulnerability, it means the system incorrectly handles permissions during the deployment process. Specifically, a user with limited rights can trick the operator into deploying a container that inherits a much more powerful service account, granting the attacker excessive, unintended control over Strimzi resources.

How does an attacker trigger this CVE-2026-105312 weakness?

An attacker needs existing authenticated access as a Kubernetes tenant with permission to create Console custom resources. By modifying the container image specification within that resource, they force the operator to deploy a malicious image. This does not trigger if a tenant lacks the ability to create Console resources or if the operator is not deployed.

Is my cluster at risk according to Halo Surface Signal?

Halo Surface Signal labels this as Unlikely because the vulnerability is not an internet-facing service or edge component. It is an internal control plane issue requiring prior authenticated access within the cluster. You should focus on environments where untrusted tenants already have elevated creation privileges.

What is the first step to address this Strimzi issue?

Start by auditing your Kubernetes clusters to identify where the affected operator is running. Once located, verify which tenant users or service accounts currently hold create permissions for Console custom resources. Restricting these permissions to trusted users is the primary way to mitigate the risk of unauthorized control-plane access.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.