strimzi strimzi-kafka-operator up to 0.49.0 on Kubernetes information disclosure

Summaryinfo

A vulnerability, which was classified as problematic, has been found in strimzi strimzi-kafka-operator up to 0.49.0 on Kubernetes. Affected is an unknown function. This manipulation causes information disclosure. This vulnerability is handled as CVE-2025-66623. The attack can only be done within the local network. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic was found in strimzi strimzi-kafka-operator up to 0.49.0 on Kubernetes. Affected by this vulnerability is an unknown functionality. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:

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.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2025-66623 since 12/05/2025. The exploitation appears to be easy. The attack can only be done within the local network. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

Upgrading to version 0.49.1 eliminates this vulnerability. Applying the patch c8a14935e99c91eb0dd865431f46515da9f82ccc is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-201497). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• strimzi

Name

• strimzi-kafka-operator

Version

• 0.1
• 0.2
• 0.3
• 0.4
• 0.5
• 0.6
• 0.7
• 0.8
• 0.9
• 0.10
• 0.11
• 0.12
• 0.13
• 0.14
• 0.15
• 0.16
• 0.17
• 0.18
• 0.19
• 0.20
• 0.21
• 0.22
• 0.23
• 0.24
• 0.25
• 0.26
• 0.27
• 0.28
• 0.29
• 0.30
• 0.31
• 0.32
• 0.33
• 0.34
• 0.35
• 0.36
• 0.37
• 0.38
• 0.39
• 0.40
• 0.41
• 0.42
• 0.43
• 0.44
• 0.45
• 0.46
• 0.47
• 0.48
• 0.49.0

License

• open-source

Website

• Product: https://github.com/strimzi/strimzi-kafka-operator/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion