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

Advisory record · `GHSA-xrhh-hx36-485q`

- **Identifiers:** `GHSA-xrhh-hx36-485q` · `CVE-2025-66623`
- **State:** Confirmed
- **Severity:** CVSS 7.4 High
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 5 Dec 2025
- **Updated:** 5 Dec 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 5 Dec 2025, 22:02 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `io.strimzi:strimzi` (Maven): affected `>=0.47.0, <0.49.1`; fixed in `0.49.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Strimzi versions 0.47.0 up to but not including 0.49.1 (fixed in 0.49.1) create an incorrect Kubernetes Role for Kafka Connect and MirrorMaker 2 deployments that lack certain TLS or mTLS trusted-certificate or authentication settings. Code running inside those Pods, using the Pod's service account, can read any Secret in the same namespace, though it cannot list, modify or delete them. Upgrade to Strimzi 0.49.1; the source states there is no workaround for affected configurations.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.4 High, CVSS 3.1: `CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0019, the 8th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:09 UTC: First seen by agentprime
- 31 Oct 2026, 15:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-xrhh-hx36-485q)

## Sources

- [GitHub Advisory Database: GHSA-xrhh-hx36-485q](https://github.com/advisories/GHSA-xrhh-hx36-485q)
- [OSV: GHSA-xrhh-hx36-485q](https://osv.dev/vulnerability/GHSA-xrhh-hx36-485q)
- <https://github.com/strimzi/strimzi-kafka-operator/security/advisories/GHSA-xrhh-hx36-485q>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-66623>
- <https://github.com/strimzi/strimzi-kafka-operator/commit/c8a14935e99c91eb0dd865431f46515da9f82ccc>
- <https://github.com/strimzi/strimzi-kafka-operator>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-xrhh-hx36-485q>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xrhh-hx36-485q/>. Everything for agents: <https://agentprime.io/llms.txt>.