CVE-2026-27133 Strimzi All CAs from CA chain will be trusted in Kafka Connect and Kafka MirrorMaker 2 target clusters
Strimzi incorrectly trusts all CAs in a chain, allowing Kafka Connect or MirrorMaker to accept connections signed by unintended CAs, bypassing TLS validation.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-27133?
CVE-2026-27133 is a medium-severity vulnerability in strimzi-kafka-operator, published on 20 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
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.
Which versions are affected by CVE-2026-27133?
It affects 1 product.
Products include Linuxfoundation Strimzi.
How do I fix CVE-2026-27133?
No fix has been published for CVE-2026-27133 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-27133 being exploited?
There is no known exploitation of CVE-2026-27133 in the wild and no public exploit code.
Other vulnerabilities in strimzi-kafka-operator
Sources
Also known as GHSA-6x85-j2f7-4xc5.