CVE-2025-66623: Strimzi Strimzi Allows Unrestricted Access To Vulnerability

Q: What is CVE-2025-66623?

CVE-2025-66623 is a security vulnerability in Strimzi involving Strimzi allows unrestricted access to all Secrets in the same Kubernetes namespace from Kafka Connect and MirrorMaker 2 operands under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.

Q: Which Strimzi versions are affected?

Affected versions include releases prior to 0.49.1 across affected packages: io.strimzi:strimzi.

Q: What version fixes CVE-2025-66623?

Upgrading to 0.49.1 (or the latest patched release for your respective branch) resolves the vulnerability.

Q: Is strimzi affected?

Yes, io.strimzi:strimzi is affected in releases prior to 0.49.1. Upgrade your dependency to 0.49.1 or later.

Q: What is the CVSS score of CVE-2025-66623?

CVE-2025-66623 has a CVSS v3.1 base score of 7.4 (HIGH) with vector string CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N.

Q: What CWE is associated with CVE-2025-66623?

CVE-2025-66623 is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).

Q: How can I check Maven dependencies for CVE-2025-66623?

Run the dependency tree command: 'mvn dependency:tree -Dincludes=io.strimzi'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.

HIGH

Advisory Identifier: GHSA-xrhh-hx36-485q

CVSS 7.4

CWE-200 CWE-863

Published 2025-12-05

Advisory Summary

CVE-2025-66623 is a HIGH (CVSS 7.4) strimzi allows unrestricted access to vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Strimzi libraries in the Maven ecosystem. The issue involves strimzi allows unrestricted access to all secrets in the same kubernetes namespace from kafka connect and mirrormaker 2 operands. Remediation is available by upgrading affected packages to version 0.49.1.

CVE-2025-66623 at a Glance

CVE Identifier CVE-2025-66623

GHSA Identifier GHSA-xrhh-hx36-485q

Severity HIGH

CVSS v3.1 Base Score 7.4

CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Affected Product Strimzi

Package Ecosystem Maven

Published Date 2025-12-05

Last Updated 2025-12-05

Security Impact

CVSS: 7.4

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N).

Attack Vector Adjacent (AV:A)

Attack Complexity Low (AC:L)

Privileges Required None (PR:N)

User Interaction None (UI:N)

Scope Changed (S:C)

Confidentiality High (C:H)

Integrity None (I:N)

Availability None (A:N)

How to Fix CVE-2025-66623

To remediate this vulnerability, upgrade all affected Strimzi dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

io.strimzi:strimzi fixed: 0.49.1

<dependency>
    <groupId>io.strimzi</groupId>
    <artifactId>strimzi</artifactId>
    <version>0.49.1</version>
</dependency>

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=io.strimzi

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2025-66623, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=io.strimzi

Analyze the terminal output to locate any version of Strimzi in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.49.1), your application is affected.

Note: The mvn dependency:tree -Dincludes=io.strimzi command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In Strimzi, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

CVE-2025-66623 Affected Strimzi Versions

1 component(s)

Fixed Versions:

0.49.1

Product / Package	Ecosystem	Affected Versions	Fixed Version
io.strimzi:strimzi maven/io.strimzi/strimzi	Maven	≥ 0.47.0 < 0.49.1	0.49.1

References

GitHub Advisory / Wiki ADVISORY

https://github.com/strimzi/strimzi-kafka-operator/security/advisories/GHSA-xrhh-hx36-485q

NVD — CVE-2025-66623 NVD

https://nvd.nist.gov/vuln/detail/CVE-2025-66623

Security Fix Commit FIX COMMIT

https://github.com/strimzi/strimzi-kafka-operator/commit/c8a14935e99c91eb0dd865431f46515da9f82ccc

Strimzi Source Repository REPOSITORY

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

Frequently Asked Questions

What is CVE-2025-66623?

CVE-2025-66623 is a security vulnerability in Strimzi involving Strimzi allows unrestricted access to all Secrets in the same Kubernetes namespace from Kafka Connect and MirrorMaker 2 operands under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.

Which Strimzi versions are affected?

Affected versions include releases prior to 0.49.1 across affected packages: io.strimzi:strimzi.

What version fixes CVE-2025-66623?

Upgrading to 0.49.1 (or the latest patched release for your respective branch) resolves the vulnerability.

Is strimzi affected?

Yes, io.strimzi:strimzi is affected in releases prior to 0.49.1. Upgrade your dependency to 0.49.1 or later.

What is the CVSS score of CVE-2025-66623?

CVE-2025-66623 has a CVSS v3.1 base score of 7.4 (HIGH) with vector string CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N.

What CWE is associated with CVE-2025-66623?

CVE-2025-66623 is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).

How can I check Maven dependencies for CVE-2025-66623?

Run the dependency tree command: 'mvn dependency:tree -Dincludes=io.strimzi'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.

Machine-readable OSV JSON OSV v1.5 Schema

Normalized schema output

View Raw JSON

{
  "schema_version" : "1.4.0",
  "id" : "GHSA-xrhh-hx36-485q",
  "modified" : "2025-12-05T22:02:37Z",
  "published" : "2025-12-05T22:02:37Z",
  "aliases" : [ "CVE-2025-66623" ],
  "summary" : "Strimzi allows unrestricted access to all Secrets in the same Kubernetes namespace from Kafka Connect and MirrorMaker 2 operands",
  "details" : "### Impact\n\nIn 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:\n* Apache Kafka Connect is deployed without at least one of the following options configured:\n    * TLS encryption with configured trusted certificates (no `.spec.tls.trustedCertificates` section in the `KafkaConnect` CR)\n    * mTLS authentication (no `type: tls` in `.spec.authentication` section of the `KafkaConnect` CR)\n    * TLS encryption with configured trusted certificates for `type: oauth` authentication (no `.spec.authentication.tlsTrustedCertificates` section in the `KafkaConnect` CR)\n* Apache Kafka MirrorMaker2 is deployed without at least one of the following options configured for the target cluster:\n    * TLS encryption with configured trusted certificates (no `.spec.target.tls.trustedCertificates` section in the `KafkaConnect` CR)\n    * mTLS authentication (no `type: tls` in `.spec.target.authentication` section of the `KafkaConnect` CR)\n    * TLS encryption with configured trusted certificates for `type: oauth` authentication (no `.spec.target.authentication.tlsTrustedCertificates` section in the `KafkaConnect` CR)\n    * TLS encryption with configured trusted certificates (no `.spec.clusters[].tls.trustedCertificates` section in the `KafkaConnect` CR for the target cluster)\n    * mTLS authentication (no `type: tls` in `.spec.clusters[].authentication` section of the `KafkaConnect` CR for the target cluster)\n    * TLS encryption with configured trusted certificates for `type: oauth` authentication (no `.spec.clusters[].authentication.tlsTrustedCertificates` section in the `KafkaConnect` CR for the target cluster)\n\nWhen 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.\n\n### Patches\n\nThe issue is fixed in Strimzi 0.49.1.\n\n### Workarounds\n\nThere is no workaround for this issue when using the affected operands with the affected configurations.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "io.strimzi:strimzi"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.47.0"
      }, {
        "fixed" : "0.49.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/strimzi/strimzi-kafka-operator/security/advisories/GHSA-xrhh-hx36-485q"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-66623"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/strimzi/strimzi-kafka-operator/commit/c8a14935e99c91eb0dd865431f46515da9f82ccc"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/strimzi/strimzi-kafka-operator"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200", "CWE-863" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-12-05T22:02:37Z",
    "nvd_published_at" : "2025-12-05T19:15:52Z"
  }
}

CVSS V3

7.4 HIGH