CVE-2026-55225

HIGHPre-NVD 8.08.0
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: secondary
Trending — 3 sources updated this week
8.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.0Exploit: None knownExposed: 0

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 Strimzi 1.0.0 and earlier, an attacker who can create a Kafka custom resource can set Kafka.spec.entityOperator watchedNamespace to a target namespace, causing the Cluster Operator to create a Role with full Secret CRUD permissions there and bind it to the Entity Operator ServiceAccount in the attacker's namespace. The attacker can mint a token for that ServiceAccount and read or write Secrets in any target namespace where the Cluster Operator has been granted permissions, regardless of STRIMZI_NAMESPACE. This issue is fixed in versions 1.0.1 and 1.1.0.

CVSS v3
8.0
EG Score
8.0(low)
EG Risk
36(Track)
EG Risk 36/100SSVC: Track

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
Severity80% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

June 18, 2026

Last Modified

September 16, 2026

Advisory Details (6)

Auto-updated Sep 15, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

1.1.0

Patch available: strimzi/strimzi-kafka-operator 1.1.0

https://github.com/strimzi/strimzi-kafka-operator/releases/tag/1.1.0
github_release Patch Available

1.0.1

Patch available: strimzi/strimzi-kafka-operator 1.0.1

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

commit f6c5207ba7ec (strimzi/strimzi-kafka-operator)

Fix landed in strimzi/strimzi-kafka-operator commit f6c5207ba7ec — awaiting tagged release

https://github.com/strimzi/strimzi-kafka-operator/commit/f6c5207ba7ec89b46ce6720b8638d647e556a261
github_commit

commit b3bfeffcc307 (strimzi/strimzi-kafka-operator)

Fix landed in strimzi/strimzi-kafka-operator commit b3bfeffcc307 — awaiting tagged release

https://github.com/strimzi/strimzi-kafka-operator/commit/b3bfeffcc30754c3e62e6f4afd8a76942cac440d
github_pr

Added enable flag for topic and user operators watched namespace

Fix merged in strimzi/strimzi-kafka-operator PR #12844 on 2026-06-18 — awaiting tagged release

https://github.com/strimzi/strimzi-kafka-operator/pull/12844
github Patch Available

Cross-namespace privilege escalation via `Kafka.spec.entityOperator` · Advisory · strimzi/strimzi-kafka-operator · GitHub

https://github.com/strimzi/strimzi-kafka-operator/security/advisories/GHSA-mw9r-p8xp-wx96

Vendor Advisories for CVE-2026-55225(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcluster-operator2026-08-12redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
io.strimzi:strimzi0.10.0 ... 1.0.0-RC2 (81 versions)1.0.1—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 24× 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.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 19:31 UTCEPSS rescore
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 13:43 UTCEG score recompute
  5. 2026-09-16 13:43 UTCVendor advisory
  6. 2026-09-16 12:21 UTCEG score recompute
  7. 2026-09-16 12:21 UTCVendor advisory
  8. 2026-09-15 20:47 UTCEG score recompute
  9. 2026-09-15 20:47 UTCVendor advisory
  10. 2026-09-15 19:50 UTCEG score recompute
  11. 2026-09-15 19:50 UTCVendor advisory
  12. 2026-09-15 18:37 UTCEG score recompute
  13. 2026-09-15 18:37 UTCVendor advisory
  14. 2026-09-15 17:24 UTCVendor advisory
  15. 2026-09-14 02:22 UTCVendor advisory
  16. 2026-09-13 14:01 UTCVendor advisory
  17. 2026-08-30 21:12 UTCVendor advisory
  18. 2026-08-24 22:21 UTCVendor advisory
  19. 2026-08-24 01:38 UTCVendor advisory
  20. 2026-08-23 14:41 UTCVendor advisory
  21. 2026-08-23 03:46 UTCVendor advisory
  22. 2026-08-21 17:36 UTCVendor advisory
  23. 2026-08-21 06:21 UTCVendor advisory
  24. 2026-08-20 19:07 UTCVendor advisory
  25. 2026-08-20 08:11 UTCVendor advisory
Show 14 more
  1. 2026-08-19 08:04 UTCVendor advisory
  2. 2026-08-17 07:44 UTCVendor advisory
  3. 2026-08-16 20:47 UTCVendor advisory
  4. 2026-08-16 08:08 UTCVendor advisory
  5. 2026-08-15 21:12 UTCVendor advisory
  6. 2026-08-15 09:07 UTCVendor advisory
  7. 2026-08-14 21:34 UTCVendor advisory
  8. 2026-08-14 10:38 UTCVendor advisory
  9. 2026-08-13 23:42 UTCVendor advisory
  10. 2026-08-13 12:42 UTCVendor advisory
  11. 2026-07-30 22:33 UTCEG score recompute
  12. 2026-07-26 18:48 UTCEG score recompute
  13. 2026-07-23 03:20 UTCEG score recompute
  14. 2026-06-18 13:08 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-55225?
CVE-2026-55225 is a high vulnerability published on June 18, 2026. Strimzi provides a way to run an Apache Kafka cluster on Kubernetes or OpenShift in various deployment configurations. In Strimzi 1.0.0 and earlier, an attacker who can create a Kafka custom resource can set Kafka.spec.entityOperator watchedNamespace to a target namespace, causing the Cluster…
When was CVE-2026-55225 disclosed?
CVE-2026-55225 was first published in the National Vulnerability Database on June 18, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55225 actively exploited?
CVE-2026-55225 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.1% of all scored CVEs.
What is the CVSS score of CVE-2026-55225?
CVE-2026-55225 has a CVSS v3 base score of 8.0 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-55225?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55225, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55225

Explore →

Is Your Infrastructure Affected by CVE-2026-55225?

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

Start Free Scan →Browse All CVEs