CVE-2026-27134

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 71% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

Published

February 21, 2026

Last Modified

July 15, 2026

Advisory Details (5)

Auto-updated Jun 30, 2026
🔬 Proof of concept available. Patch available. Sources: redhat, github_release, github.
redhat
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-27134.json
redhat

2441564 – (CVE-2026-27134) CVE-2026-27134 strimzi-kafka-operator: Strimzi: Unauthorized authentication via misconfigured mTLS CA chain

https://bugzilla.redhat.com/show_bug.cgi?id=2441564
redhatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2026-27134
githubMentions a patch (unverified)🟡 PoC Available

All CAs from a custom CA chain consisting of multiple CAs are trusted for mTLS user authentication · Advisory · strimzi/strimzi-kafka-operator · GitHub

https://github.com/strimzi/strimzi-kafka-operator/security/advisories/GHSA-2qwx-rq6j-8r6j
github_release Patch Available

0.50.1

Patch available: strimzi/strimzi-kafka-operator 0.50.1

https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.50.1

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 122 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-09 07:55 UTCOSV refresh
  3. 2026-10-08 17:11 UTCEPSS rescore
  4. 2026-10-07 23:47 UTCEPSS rescore
  5. 2026-10-06 15:17 UTCEPSS rescore
  6. 2026-10-05 17:42 UTCEPSS rescore
  7. 2026-10-04 23:21 UTCEPSS rescore
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-01 19:49 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-28 13:51 UTCEPSS rescore
  12. 2026-09-26 15:58 UTCEPSS rescore
  13. 2026-09-26 00:26 UTCEPSS rescore
  14. 2026-09-20 20:15 UTCEPSS rescore
  15. 2026-09-20 20:15 UTCEPSS rescore
  16. 2026-09-19 14:33 UTCOSV refresh
  17. 2026-09-18 19:28 UTCEPSS rescore
  18. 2026-09-18 19:27 UTCEPSS rescore
  19. 2026-09-17 19:30 UTCEPSS rescore
  20. 2026-09-16 14:08 UTCEPSS rescore
  21. 2026-09-16 05:15 UTCEPSS rescore
  22. 2026-09-13 16:47 UTCEPSS rescore
  23. 2026-09-12 15:01 UTCEPSS rescore
  24. 2026-09-11 14:52 UTCEPSS rescore
  25. 2026-09-10 09:34 UTCEPSS rescore
Show 75 more
  1. 2026-09-08 22:00 UTCEPSS rescore
  2. 2026-09-07 16:01 UTCEPSS rescore
  3. 2026-09-06 13:47 UTCEPSS rescore
  4. 2026-09-06 13:47 UTCEPSS rescore
  5. 2026-09-04 05:06 UTCEPSS rescore
  6. 2026-09-02 14:11 UTCEPSS rescore
  7. 2026-09-01 13:53 UTCEPSS rescore
  8. 2026-09-01 04:39 UTCEPSS rescore
  9. 2026-08-31 18:04 UTCOSV refresh
  10. 2026-08-30 19:17 UTCEPSS rescore
  11. 2026-08-30 01:22 UTCEPSS rescore
  12. 2026-08-28 21:41 UTCEPSS rescore
  13. 2026-08-27 14:25 UTCEPSS rescore
  14. 2026-08-26 14:46 UTCEPSS rescore
  15. 2026-08-25 13:48 UTCEPSS rescore
  16. 2026-08-23 00:19 UTCEPSS rescore
  17. 2026-08-21 23:49 UTCEPSS rescore
  18. 2026-08-20 22:55 UTCEPSS rescore
  19. 2026-08-19 17:03 UTCEPSS rescore
  20. 2026-08-18 13:48 UTCEPSS rescore
  21. 2026-08-17 13:47 UTCEPSS rescore
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 09:18 UTCEG score recompute
  26. 2026-08-13 22:00 UTCEPSS rescore
  27. 2026-08-13 01:22 UTCEG score recompute
  28. 2026-08-12 13:50 UTCEPSS rescore
  29. 2026-08-12 01:30 UTCEG score recompute
  30. 2026-08-11 13:42 UTCEPSS rescore
  31. 2026-08-11 06:50 UTCEG score recompute
  32. 2026-08-11 00:00 UTCEPSS rescore
  33. 2026-08-09 21:35 UTCEG score recompute
  34. 2026-08-09 13:46 UTCEPSS rescore
  35. 2026-08-09 08:56 UTCEG score recompute
  36. 2026-08-08 16:37 UTCEPSS rescore
  37. 2026-08-07 21:05 UTCEG score recompute
  38. 2026-08-06 13:46 UTCEPSS rescore
  39. 2026-08-06 03:16 UTCEG score recompute
  40. 2026-08-05 19:17 UTCEPSS rescore
  41. 2026-08-04 15:10 UTCEPSS rescore
  42. 2026-08-03 10:36 UTCEPSS rescore
  43. 2026-08-02 19:52 UTCEG score recompute
  44. 2026-08-02 02:26 UTCEPSS rescore
  45. 2026-08-01 04:16 UTCEPSS rescore
  46. 2026-07-30 16:27 UTCEPSS rescore
  47. 2026-07-30 01:30 UTCEPSS rescore
  48. 2026-07-28 15:36 UTCEPSS rescore
  49. 2026-07-26 14:54 UTCEPSS rescore
  50. 2026-07-26 14:54 UTCEPSS rescore
  51. 2026-07-25 14:18 UTCEPSS rescore
  52. 2026-07-25 14:17 UTCEPSS rescore
  53. 2026-07-24 14:17 UTCEPSS rescore
  54. 2026-07-23 14:18 UTCEPSS rescore
  55. 2026-07-23 14:18 UTCEPSS rescore
  56. 2026-07-23 03:07 UTCEG score recompute
  57. 2026-07-22 14:08 UTCEPSS rescore
  58. 2026-07-22 14:08 UTCEPSS rescore
  59. 2026-07-21 15:24 UTCEPSS rescore
  60. 2026-07-21 15:24 UTCEPSS rescore
  61. 2026-07-20 17:08 UTCEPSS rescore
  62. 2026-07-20 17:08 UTCEPSS rescore
  63. 2026-07-19 14:31 UTCEPSS rescore
  64. 2026-07-19 14:31 UTCEPSS rescore
  65. 2026-07-19 02:29 UTCEPSS rescore
  66. 2026-07-18 10:04 UTCEPSS rescore
  67. 2026-07-18 10:04 UTCEPSS rescore
  68. 2026-07-18 07:29 UTCOSV refresh
  69. 2026-07-16 17:03 UTCEPSS rescore
  70. 2026-07-16 17:03 UTCEPSS rescore
  71. 2026-07-15 16:57 UTCEPSS rescore
  72. 2026-07-15 16:57 UTCEPSS rescore
  73. 2026-07-15 02:00 UTCEPSS rescore
  74. 2026-07-15 02:00 UTCEPSS rescore
  75. 2026-07-13 22:30 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-27134?
CVE-2026-27134 is a high vulnerability published on February 21, 2026. 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…
When was CVE-2026-27134 disclosed?
CVE-2026-27134 was first published on February 21, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-27134 actively exploited?
CVE-2026-27134 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-27134?
CVE-2026-27134 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-27134?
A fix for CVE-2026-27134 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-27134

Explore →

Is Your Infrastructure Affected by CVE-2026-27134?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs