Skip to content
Connect AISign inSign up free
CVE-2026-271348.1HighCWE-296

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

strimzi · strimzi-kafka-operator

Affected: strimzi-kafka-operator · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.4%probability of exploitation in the next 30 days
33rd percentile
050100

Higher than 33% of scored CVEs

8.1HighCVSS 3.1
LowHigh

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • strimzi · strimzi-kafka-operator>= 0.49.0, < 0.50.1

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
strimzi
Published
February 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-27134 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References