dbcve.org
StrimziApplication · Linuxfoundation

CVE-2026-27133

MEDIUM · 5.9 CVSS v3.1 Published 2026-02-20
Fix available
A fix is available. Upgrade to 0.50.1 or later.
See remediation →
65/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Strimzi Kafka Connect and Kafka MirrorMaker 2 operands, when a CA certificate chain is configured as trusted, the validation logic incorrectly trusts all certificates individually signed by any CA in the chain rather than only those signed by the final/leaf CA. This allows connections to Kafka brokers using certificates from unintended CAs within the configured chain.

MitigationUpgrade Strimzi to version 0.50.1 or later to fix the CA chain validation logic, and review trusted CA certificate configurations to ensure only intended CAs are specified.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
StrimziApplication
Affected:>= 0.47.0, < 0.50.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Strimzi operator version
    Run 'kubectl get deployment -n <strimzi-namespace> strimzi-cluster-operator -o jsonpath={.spec.template.spec.containers[0].image}' to get the operator image, then extract the version or check the CSV: 'kubectl get csv -n <strimzi-namespace> -o jsonpath={.items[0].spec.version}'
    Affected if The Strimzi version is 0.47.0 through 0.50.0 (inclusive)
  2. Check for Kafka Connect deployments
    Run 'kubectl get kafkaconnect -A' to list all KafkaConnect custom resources in the cluster
    Affected if Any KafkaConnect resource exists in the affected Strimzi version range
  3. Check for Kafka MirrorMaker 2 deployments
    Run 'kubectl get kafkamirrormaker2 -A' to list all KafkaMirrorMaker2 custom resources in the cluster
    Affected if Any KafkaMirrorMaker2 resource exists in the affected Strimzi version range
  4. Inspect TLS configuration for trusted CA certificates
    For each KafkaConnect or KafkaMirrorMaker2 resource, check the TLS configuration section: 'kubectl get kafkaconnect <name> -n <namespace> -o json' and look for 'tls' or 'authentication' sections with 'certificateTrustStore' or 'trustedCertificates' defined
    Affected if Custom CA certificates or certificate trust chains are configured in the TLS settings
  5. Verify certificate validation behavior
    Review the KafkaConnect or KafkaMirrorMaker2 TLS configuration to confirm custom CA chains are in use rather than default system trust store, particularly looking at any 'ssl.truststore' or CA certificate definitions
    Affected if A custom CA certificate chain is explicitly configured for TLS connections to brokers

You are affected if running Strimzi version 0.47.0-0.50.0 with Kafka Connect or MirrorMaker 2 and have custom CA certificates configured for TLS connections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.50.1 or later
Fixed in 0.50.1
Interim mitigation

Upgrade Strimzi to version 0.50.1 or later to fix the CA chain validation logic, and review trusted CA certificate configurations to ensure only intended CAs are specified.

Recommended fix High confidence

Strimzi 0.50.1

  1. Upgrade Strimzi to version 0.50.1 or later
  2. Verify the upgrade in a test environment before production deployment
  3. Review the Strimzi 0.50.1 release notes for any migration notes or configuration changes
  4. After upgrade, verify that Kafka Connect and Kafka MirrorMaker 2 correctly validate certificates using only the intended CA chain (the last CA in the chain)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Strimzi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27133 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27133 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data