CVE-2026-61459
Argument injection in MCP Server Kubernetes allows exfiltration of operator bearer tokens.
Is CVE-2026-61459 being exploited?
Not confirmed. CVE-2026-61459 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 2.1% probability of exploitation in the next 30 days.
How severe is CVE-2026-61459?
CVE-2026-61459 is rated Critical with a CVSS score of 9.3. 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-61459?
Yes. A fix has been recorded for CVE-2026-61459. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-61459 affect?
CVE-2026-61459 affects MCP Server Kubernetes < 3.9.0, kubectl_get / kubectl_describe / kubectl_delete structured tools, Kubernetes clusters managed by MCP operators. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-61459?
Upgrade to MCP Server Kubernetes 3.9.0 immediately and rotate operator/service-account tokens.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can inject --server via resource names, redirect kubectl to malicious API, exfiltrate operator bearer token and achieve full cluster compromise.
Immediate action required
- affected< 3.9.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.