Answer in brief
CVE-2026-27134 records a High severity (CVSS 8.1) vulnerability in Strimzi: All CAs from a custom CA chain consisting of multiple CAs are trusted for mTLS user autentication. The current sources do not mark it as known exploited. The current feed maps Red Hat/io.strimzi-strimzi (generic), Red Hat/io.strimzi-strimzi-drain-cleaner (generic), strimzi/strimzi-kafka-operator (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Red Hat/io.strimzi-strimzi (generic), Red Hat/io.strimzi-strimzi-drain-cleaner (generic), strimzi/strimzi-kafka-operator (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Red Hat/io.strimzi-strimzigeneric | * | Not reported |
| Red Hat/io.strimzi-strimzi-drain-cleanergeneric | * | Not reported |
| strimzi/strimzi-kafka-operatorgeneric | >=0.49.0 <0.50.1 | 0.50.1 |
Published upstream
Feb 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.