CVE-2026-27134
mTLS auth bypass in Strimzi with multistage CA chain.
Is CVE-2026-27134 being exploited?
Not confirmed. CVE-2026-27134 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.36% probability of exploitation in the next 30 days.
How severe is CVE-2026-27134?
CVE-2026-27134 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-27134?
Yes. A fix has been recorded for CVE-2026-27134. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-27134 affect?
CVE-2026-27134 affects Strimzi 0.49.0-0.50.0 (multistage CA chain), Kubernetes/OpenShift deployments using Strimzi. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-27134?
Upgrade to Strimzi 0.50.1+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Allows authentication with any cert in the multi-CA chain, bypassing mTLS and enabling unauthorized Kafka access.
Patch when possible
- affected>= 0.49.0 and < 0.50.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.