CVE-2026-27133: Strimzi All CAs from CA chain will be trusted in Kafka Connect and Kafka MirrorMaker 2 target clusters
Strimzi provides a way to run an Apache Kafka cluster on Kubernetes or OpenShift in various deployment configurations. From 0.47.0 to before 0.50.1, when a chain consisting of multiple CA (Certificate Authority) certificates is used in the trusted certificates configuration of a Kafka Connect operand or of the target cluster in the Kafka MirrorMaker 2 operand, all of the certificates that are part of the CA chain will be trusted individually when connecting to the Apache Kafka cluster. Due to this error, the affected operand (Kafka Connect or Kafka MirrorMaker 2) might accept connections to Kafka brokers using server certificates signed by one of the other CAs in the CA chain and not just by the last CA in the chain. This issue is fixed in Strimzi 0.50.1.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-27133?
CVE-2026-27133 is classified as a medium severity vulnerability.
How do I fix CVE-2026-27133?
To remediate CVE-2026-27133, upgrade Strimzi Kafka Operator to version 0.50.1 or later.
What versions are affected by CVE-2026-27133?
CVE-2026-27133 affects Strimzi Kafka Operator versions from 0.47.0 up to but not including 0.50.1.
What are the implications of CVE-2026-27133?
CVE-2026-27133 allows all certificate authorities from a CA chain to be trusted in Kafka Connect and Kafka MirrorMaker 2 target clusters, potentially leading to security risks.
Is there a workaround for CVE-2026-27133?
There is no recommended workaround for CVE-2026-27133; upgrading to the secure version is the only solution.