CVE-2026-55225highCWE-250CWE-269CWE-441

CVE-2026-55225: high-severity vulnerability in strimzi-kafka-operator

Strimzi: Cross-namespace privilege escalation via `Kafka.spec.entityOperator`

Published · Updated

Follow this CVE+ Monitor strimzi-kafka-operator+ Monitor io.strimzi:strimzi

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

21Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 8epss 0.3%
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:3.1/AV:A/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Affected products
strimzi · strimzi-kafka-operator
Related CVEs — strimzi-kafka-operator

In the same product, most dangerous first.

CVE-2026-27134HIGHStrimzi: All CAs from a custom CA chain consisting of multiple CAs are trusted for mTLS user autenticationEPSS 0.4%CVE-2026-55226MEDIUMStrimzi: Unrestricted access to all Secrets within namespace watched by the Topic operatorEPSS 0.3%CVE-2026-27133MEDIUMStrimzi All CAs from CA chain will be trusted in Kafka Connect and Kafka MirrorMaker 2 target clustersEPSS 0.2%CVE-2025-66623HIGHStrimzi allows unrestricted access to all Secrets in the same Kubernetes namespace from Kafka Connect and MirrorMaker 2 operandsEPSS 0.2%