Answer in brief
CVE-2026-55226 records a Medium severity vulnerability in Strimzi: Unrestricted access to all Secrets within namespace watched by the Topic operator. The current sources do not mark it as known exploited. The current feed maps strimzi/strimzi-kafka-operator (generic), io.strimzi:strimzi (maven). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps strimzi/strimzi-kafka-operator (generic), io.strimzi:strimzi (maven). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| strimzi/strimzi-kafka-operatorgeneric | < 1.0.1 | Not reported |
| io.strimzi:strimzimaven | <=1.0.0 | 1.0.1 |
Published upstream
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 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, deploying only the Topic Operator or only the User Operator through the Kafka custom resource leaves the Entity Operator ServiceAccount with RBAC permissions for both components. The excess permissions can allow access to KafkaUser custom resources and Secrets when the User Operator is absent, or access to KafkaTopic custom resources when the Topic Operator is absent. This issue is fixed in versions 1.0.1 and 1.1.0.
Quoted source text, attributed separately from HOL analysis.