CVE-2026-55226

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 5.4 under the CNA's CVSS (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: cna:github_m
5.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: —CVSS: 5.4Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Strimzi: Unrestricted access to all Secrets within namespace watched by the Topic operator

Impact

When only the Topic or only the User operators are deployed as part of the Entity Operator in the Kafka custom resource, the RBAC rights are not following the principle of least-privilege and the Entity Operator ServiceAccount still has access rights corresponding to both operators. That might allow the ServiceAccount to access KafkaUser custom resources and Secrets when the User operator is not deployed and access KafkaTopic custom resources when the Topic operator is not deployed.

Patches

The issue is fixed in Strimzi 1.0.1 and 1.1.0.

Workarounds

There is no workaround for this issue.

CVSS v3
5.4
EG Score
5.4(low)
EPSS
—
KEV
Not listed

Published

June 18, 2026

Last Modified

June 18, 2026

Vendor Advisories for CVE-2026-55226(1)

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

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—

Data Freshness Timeline

(refreshed 7× in last 7d / 18× 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-07-07 04:55 UTCEG score recompute
  2. 2026-07-06 02:35 UTCEG score recompute
  3. 2026-07-05 00:15 UTCEG score recompute
  4. 2026-07-03 21:55 UTCEG score recompute
  5. 2026-07-02 19:36 UTCEG score recompute
  6. 2026-07-01 17:16 UTCEG score recompute
  7. 2026-06-30 14:56 UTCEG score recompute
  8. 2026-06-29 12:29 UTCEG score recompute
  9. 2026-06-28 10:09 UTCEG score recompute
  10. 2026-06-27 07:47 UTCEG score recompute
  11. 2026-06-26 05:28 UTCEG score recompute
  12. 2026-06-25 03:07 UTCEG score recompute
  13. 2026-06-24 00:48 UTCEG score recompute
  14. 2026-06-22 22:29 UTCEG score recompute
  15. 2026-06-21 20:09 UTCEG score recompute
  16. 2026-06-20 17:50 UTCEG score recompute
  17. 2026-06-19 15:27 UTCEG score recompute
  18. 2026-06-18 13:08 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-55226?
CVE-2026-55226 is a medium vulnerability published on June 18, 2026. Strimzi: Unrestricted access to all Secrets within namespace watched by the Topic operator Impact When only the Topic or only the User operators are deployed as part of the Entity Operator in the Kafka custom resource, the RBAC rights are not following the principle of least-privilege and the…
When was CVE-2026-55226 disclosed?
CVE-2026-55226 was first published in the National Vulnerability Database on June 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-55226?
CVE-2026-55226 has a CVSS v4.0 base score of 5.4 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-55226?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55226, 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-55226

Explore →

Is Your Infrastructure Affected by CVE-2026-55226?

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

Start Free Scan →Browse All CVEs