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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-27133
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 01:03 UTC · Revision 1
Source evidence
Strimzi All CAs from CA chain will be trusted in Kafka Connect and Kafka MirrorMaker 2 target clusters
core-osv · Original sourcePublished 20 Feb 2026, 22:38 UTC
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.
osv:CVE-2026-27133
Complete source record
{
"id": "d3c6b92823e7def123a35f6e91ed545a150d830fbacd4e20ee18655d38a758d3",
"url": "https://osv.dev/vulnerability/CVE-2026-27133",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Strimzi All CAs from CA chain will be trusted in Kafka Connect and Kafka MirrorMaker 2 target clusters",
"summary": "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.",
"evidence": "osv:CVE-2026-27133",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2026-27133",
"aliases": [
"CVE-2026-27133",
"GHSA-6x85-j2f7-4xc5"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/strimzi/strimzi-kafka-operator",
"type": "GIT",
"events": [
{
"introduced": "40b9fa269ba87283bb0651711557922b14d715b3"
},
{
"fixed": "d86dfbf4d1adf8f475e1c98cfbaf63e7b32f71c5"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "0.50.1"
}
],
"source": "DESCRIPTION"
},
{
"range": [
{
"fixed": "d86dfbf4d1adf8f475e1c98cfbaf63e7b32f71c5"
}
],
"source": "REFERENCES_TAG",
"original_tag": "0.50.1"
},
{
"cpe": "cpe:2.3:a:linuxfoundation:strimzi:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0.47.0"
},
{
"fixed": "0.50.1"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-27133.json"
}
}
],
"modified": "2026-10-28T02:30:24.970830107Z",
"provider": "osv",
"references": [
"https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.50.1",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/27xxx/CVE-2026-27133.json",
"https://github.com/strimzi/strimzi-kafka-operator/security/advisories/GHSA-6x85-j2f7-4xc5",
"https://nvd.nist.gov/vuln/detail/CVE-2026-27133"
],
"provider_metadata": {
"cwe_ids": [
"CWE-295",
"CWE-296"
],
"cna_assigner": "GitHub_M",
"unresolved_ranges": [
{
"extracted_events": [
{
"range": [
{
"introduced": "0.47.0"
},
{
"fixed": "0.51.1"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
}
]
}
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/27xxx/CVE-2026-27133.json"
}
},
"related_cves": [
{
"value": "CVE-2026-27133",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 491411,
"published_at": "2026-02-20T22:38:27.721+00:00"
}