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

Published Feb 20, 2026
·
Updated

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 Software

2 affected components
strimzi/strimzi-kafka-operator>=0.49.0<=0.50.0
linuxfoundation Strimzi Kafka Operator>=0.49.0<0.50.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Strimzi to a version that resolves this vulnerability.

    Fixed in 0.50.1
  2. Configuration

    For Strimzi versions 0.49.0 through 0.50.0 using a custom Cluster or Clients CA with a multistage CA chain of multiple CAs, workaround by configuring the custom CA to include only the single CA that should be used, instead of the full CA chain.

    Strimzi mTLS authentication (custom Cluster/Clients CA) custom CA chain provided = Provide only the single CA to be used (do not provide the full multistage CA chain consisting of multiple CAs)

Event History

Feb 20, 2026
CVE Published
via MITRE·11:05 PM
Data Sourced
via MITRE·11:05 PM
DescriptionSeverityWeakness
Feb 21, 2026
Data Sourced
via Red Hat·12:02 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·12:16 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-27134?

CVE-2026-27134 has a medium severity rating due to its potential impact on mTLS user authentication in Strimzi.

2

How do I fix CVE-2026-27134?

To fix CVE-2026-27134, you should upgrade Strimzi to version 0.50.1 or later.

3

What versions of Strimzi are affected by CVE-2026-27134?

CVE-2026-27134 affects Strimzi versions 0.49.0 through 0.50.0.

4

What is the specific issue described in CVE-2026-27134?

CVE-2026-27134 describes a vulnerability where all CAs from a custom CA chain are trusted for mTLS user authentication.

5

Who is impacted by CVE-2026-27134?

Users running Strimzi with custom CAs for mTLS authentication are impacted by CVE-2026-27134.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203