{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-27133 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-27133 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-27133 is a medium-severity vulnerability in strimzi-kafka-operator, published on 20 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-27133 and fix it if it is affected.\n\nWhat it is: CVE-2026-27133 is a medium-severity vulnerability in strimzi-kafka-operator, published on 20 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-27133 in the wild and no public exploit code.\n\nAffected product: strimzi-kafka-operator. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-27133/ (Markdown: https://insights.sbomify.com/CVE-2026-27133/index.md)","id":"CVE-2026-27133","markdown":"https://insights.sbomify.com/CVE-2026-27133/index.md","name":"CVE-2026-27133","record":{"aliases":["GHSA-6x85-j2f7-4xc5"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Kubernetes Kafka operator","requires_auth":"high_privilege","summary":"Strimzi incorrectly trusts all CAs in a chain, allowing Kafka Connect or MirrorMaker to accept connections signed by unintended CAs, bypassing TLS validation.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"strimzi","vendor":"linuxfoundation"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-296","name":"Improper Following of a Certificate's Chain of Trust"},{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Strimzi All CAs from CA chain will be trusted in Kafka Connect and Kafka MirrorMaker 2 target clusters","id":"CVE-2026-27133","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Strimzi: All CAs from a custom CA chain consisting of multiple CAs are trusted for mTLS user autentication","id":"CVE-2026-27134"},"packages":[],"prev":{"headline":"Sprig Plugin for Craft CMS potentially discloses sensitive information via Sprig Playground","id":"CVE-2026-27131"},"products":["strimzi-kafka-operator"],"published":"2026-02-20","related":[{"cvss_score":7.4,"headline":"Strimzi allows unrestricted access to all Secrets in the same Kubernetes namespace from Kafka Connect and MirrorMaker 2 operands","id":"CVE-2025-66623","kev_date_added":null,"published":"2025-12-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-25","vendors":["strimzi"]},"summary":"Strimzi incorrectly trusts all CAs in a chain, allowing Kafka Connect or MirrorMaker to accept connections signed by unintended CAs, bypassing TLS validation.","url":"https://insights.sbomify.com/CVE-2026-27133/"}