8.1High

CVE-2026-27134Strimzi: All CAs from a custom CA chain consisting of multiple CAs are trusted for mTLS user autentication

strimzi strimzi-kafka-operator; Red Hat streams for Apache Kafka 2; Red Hat streams for Apache Kafka 3 Published: (8 months ago)

Description

Strimzi provides a way to run an Apache Kafka cluster on Kubernetes or OpenShift in various deployment configurations. In versions 0.49.0 through 0.50.0, when using a custom Cluster or Clients CA with a multistage CA chain consisting of multiple CAs, Strimzi incorrectly configures the trusted certificates for mTLS authentication on the internal as well as user-configured listeners. All CAs from the CA chain will be trusted. And users with certificates signed by any of the CAs in the chain will be able to authenticate. This issue affects only users using a custom Cluster or Clients CA with a multistage CA chain consisting of multiple CAs. It does not affect users using the Strimzi-managed Cluster and Clients CAs. It also does not affect users using custom Cluster or Clients CA with only a single CA (i.e., no CA chain with multiple CAs). This issue has been fixed in version 0.50.1. To workaround this issue, instead of providing the full CA chain as the custom CA, users can provide only the single CA that should be used.

Weakness (CWE): CWE-287CWE-295CWE-296

Data: CVE.org, NVD, CISA KEV, FIRST EPSS, Ubuntu. Published as the sources state it, in English.

Affected products and versions

VendorProductVersions
linuxfoundation strimzi kafka operator 0.49.0 – < 0.50.1
Red Hat streams for Apache Kafka 2 all versions
Red Hat streams for Apache Kafka 3 all versions
strimzi strimzi-kafka-operator >= 0.49.0, < 0.50.1

References and patches

CPE matches (NVD) (1)

  • cpe:2.3:a:linuxfoundation:strimzi_kafka_operator:*:*:*:*:*:*:*:* ≥ 0.49.0 < 0.50.1