CVE-2026-27133
- Source
- https://cve.org/CVERecord?id=CVE-2026-27133
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-27133.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-27133
- Aliases
-
- GHSA-6x85-j2f7-4xc5
- Published
- 2026-02-20T22:38:27.721Z
- Modified
- 2026-03-01T07:33:30.916271Z
- Severity
-
- 5.9 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N CVSS Calculator
- Summary
- Strimzi All CAs from CA chain will be trusted in Kafka Connect and Kafka MirrorMaker 2 target clusters
- Details
-
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.
- Database specific
{ "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/27xxx/CVE-2026-27133.json", "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-295", "CWE-296" ] }- References