CVE-2025-66623: Strimzi allows unrestricted access to all Secrets in the same Kubernetes namespace from Kafka Connect and MirrorMaker 2 operands
Impact
In some situations, Strimzi creates an incorrect Kubernetes Role which grants the Apache Kafka Connect and Apache Kafka MirrorMaker 2 operands the GET access to all Kubernetes Secrets that exist in the given Kubernetes namespace. The exact scenario when this happens is when: Apache Kafka Connect is deployed without at least one of the following options configured: TLS encryption with configured trusted certificates (no .spec.tls.trustedCertificates section in the KafkaConnect CR) mTLS authentication (no type: tls in .spec.authentication section of the KafkaConnect CR) TLS encryption with configured trusted certificates for type: oauth authentication (no .spec.authentication.tlsTrustedCertificates section in the KafkaConnect CR) Apache Kafka MirrorMaker2 is deployed without at least one of the following options configured for the target cluster: TLS encryption with configured trusted certificates (no .spec.target.tls.trustedCertificates section in the KafkaConnect CR) mTLS authentication (no type: tls in .spec.target.authentication section of the KafkaConnect CR) TLS encryption with configured trusted certificates for type: oauth authentication (no .spec.target.authentication.tlsTrustedCertificates section in the KafkaConnect CR) TLS encryption with configured trusted certificates (no .spec.clusters[].tls.trustedCertificates section in the KafkaConnect CR for the target cluster) mTLS authentication (no type: tls in .spec.clusters[].authentication section of the KafkaConnect CR for the target cluster) TLS encryption with configured trusted certificates for type: oauth authentication (no .spec.clusters[].authentication.tlsTrustedCertificates section in the KafkaConnect CR for the target cluster)
When the operands configured as described above are deployed with Strimzi >= 0.47.0 and <= 0.49.0, any code running within their Pods and using their Service Account for authentication will be able to GET any Kubernetes Secret from the same namespace. This can be done by executing 3rd party tools from the Pods. Or directly from the Kafka Connect code, for example, using configuration providers or HTTP connectors. The Pods are allowed to only GET the Secrets. They are not allowed to list, watch, modify, or delete the Secrets.
Patches
The issue is fixed in Strimzi 0.49.1.
Workarounds
There is no workaround for this issue when using the affected operands with the affected configurations.
Other sources
Strimzi provides a way to run an Apache Kafka cluster on Kubernetes or OpenShift in various deployment configurations. From 0.47.0 and prior to 0.49.1, in some situations, Strimzi creates an incorrect Kubernetes Role which grants the Apache Kafka Connect and Apache Kafka MirrorMaker 2 operands the GET access to all Kubernetes Secrets that exist in the given Kubernetes namespace. The issue is fixed in Strimzi 0.49.1.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-66623?
CVE-2025-66623 is classified as a medium severity vulnerability due to its potential to expose sensitive resources.
How do I fix CVE-2025-66623?
To fix CVE-2025-66623, upgrade Strimzi to version 0.49.1 or later to ensure proper Kubernetes Role permissions.
What are the affected versions for CVE-2025-66623?
CVE-2025-66623 affects Strimzi versions from 0.47.0 up to, but not including, 0.49.1.
What is the impact of CVE-2025-66623?
The impact of CVE-2025-66623 includes unauthorized access to resources managed by Apache Kafka Connect and MirrorMaker due to incorrect role assignments.
Who is affected by CVE-2025-66623?
Organizations using Strimzi versions between 0.47.0 and 0.49.1 are affected by CVE-2025-66623.