Affects Kubernetes addon-manager in clusters; allows cluster-wide secret disclosure and CSR approval—impactful across organizations using Kubernetes.
CVE-2026-75924
Kubernetes addon-manager role permits reading all secrets and approving CSRs from a compromised pod.
Is CVE-2026-75924 being exploited?
Not confirmed. CVE-2026-75924 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.16% probability of exploitation in the next 30 days.
How severe is CVE-2026-75924?
CVE-2026-75924 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-75924?
Not known from our data. No patch reference has been recorded for CVE-2026-75924, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-75924 affect?
CVE-2026-75924 affects Kubernetes addon-manager (managed-serviceaccount), Kubernetes clusters (all namespaces), ClusterRole/CSR approval workflows. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-75924?
Remove/restrict addon-manager ClusterRole, rotate secrets/tokens, isolate/replace pods, harden CSR approvals, apply patch when published.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
A compromised addon-manager pod can read any namespace secret and approve CSRs to escalate privileges within the cluster.
Immediate action required