CVE-2026-27134

{"id": "CVE-2026-27134", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 8.1, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 2.2}]}, "published": "2026-02-21T00:16:15.940", "references": [{"url": "https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.50.1", "tags": ["Product", "Release Notes"], "source": "security-advisories@github.com"}, {"url": "https://github.com/strimzi/strimzi-kafka-operator/security/advisories/GHSA-2qwx-rq6j-8r6j", "tags": ["Vendor Advisory"], "source": "security-advisories@github.com"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-287"}, {"lang": "en", "value": "CWE-295"}, {"lang": "en", "value": "CWE-296"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "Strimzi proporciona una forma de ejecutar un cl\u00faster de Apache Kafka en Kubernetes u OpenShift en varias configuraciones de despliegue. En las versiones 0.49.0 a 0.50.0, al usar una CA de cl\u00faster o clientes personalizada con una cadena de CA multifase que consta de m\u00faltiples CA, Strimzi configura incorrectamente los certificados de confianza para la autenticaci\u00f3n mTLS tanto en los oyentes internos como en los configurados por el usuario. Todas las CA de la cadena de CA ser\u00e1n de confianza. Y los usuarios con certificados firmados por cualquiera de las CA de la cadena podr\u00e1n autenticarse. Este problema afecta solo a los usuarios que usan una CA de cl\u00faster o clientes personalizada con una cadena de CA multifase que consta de m\u00faltiples CA. No afecta a los usuarios que usan las CA de cl\u00faster y clientes gestionadas por Strimzi. Tampoco afecta a los usuarios que usan una CA de cl\u00faster o clientes personalizada con solo una \u00fanica CA (es decir, sin cadena de CA con m\u00faltiples CA). Este problema ha sido solucionado en la versi\u00f3n 0.50.1. Como soluci\u00f3n alternativa a este problema, en lugar de proporcionar la cadena de CA completa como la CA personalizada, los usuarios pueden proporcionar solo la \u00fanica CA que debe usarse."}], "lastModified": "2026-02-25T18:54:50.690", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:linuxfoundation:strimzi_kafka_operator:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "D7602B49-F655-4497-890A-3FA585C739FD", "versionEndExcluding": "0.50.1", "versionStartIncluding": "0.49.0"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}