Most recent entries from all

EUVD-2026-369598

fkie_cve-2026-55226

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.

GHSA-r427-j2h7-wv3m — Strimzi: Unrestricted access to all Secrets within namespace watched by the Topic operator

Affected: Maven: io.strimzi:strimzi

### 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.