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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.4 | High | 3.1 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N | 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
Sources
- GitHub Advisory Database: GHSA-xrhh-hx36-485q
- OSV: GHSA-xrhh-hx36-485q
- github.com/strimzi/strimzi-kafka-operator/security/advisories/GHSA-xrhh-hx36-485q
- nvd.nist.gov/vuln/detail/CVE-2025-66623
- github.com/strimzi/strimzi-kafka-operator/commit/c8a14935e99c91eb0dd865431f46515da9f82ccc
- github.com/strimzi/strimzi-kafka-operator