Sign in
Deutsch English Español Polski
High

Strimzi allows unrestricted access to all Secrets in the same Kubernetes namespace from Kafka Connect and MirrorMaker 2 operands

  • Disclosed: 05.12.2025
  • Updated: 11.10.2026 12:22

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.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Java / Kotlin (Maven) io.strimzi:strimzi >= 0.47.0, < 0.49.1 0.49.1

References

CVSS score 7.4/10
CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Weakness (CWE)
CWE-200, CWE-863
Platform
Java / Kotlin (Maven)
Package
io.strimzi:strimzi
Disclosed
05.12.2025
Updated
11.10.2026 12:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-xrhh-hx36-485q - CC BY 4.0

Vulnerability history: io.strimzi:strimzi

All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.

Total entries
4
First → latest
06.2024 06.2026
Without a fix
1
Exploited in attacks
0

Severity breakdown

  • High 3
  • Medium 1

Disclosures per year

  1. Strimzi: Unrestricted access to all Secrets within namespace watched by the Topic operator
    Medium · 5.4 CVE-2026-55226 < 1.0.1 1.0.1
  2. Strimzi: Cross-namespace privilege escalation via `Kafka.spec.entityOperator`
    High · 8.0 CVE-2026-55225 < 1.0.1 1.0.1
  3. Strimzi allows unrestricted access to all Secrets in the same Kubernetes namespace from Kafka Connect and MirrorMaker 2 operands this entry
    High · 7.4 CVE-2025-66623 >= 0.47.0, < 0.49.1 0.49.1
  4. STRIMZI incorrect access control
    High · 7.3 CVE-2024-36543 <= 0.41.0 no fix

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Privacy policy

Free to subscribe. Unsubscribe with one click in any email.