CVE-2026-61459: MCP Server Kubernetes < 3.9.0 Argument Injection via kubectl Structured Tools
MCP Server Kubernetes before 3.9.0 contains an argument injection vulnerability in structured tools (kubectlget, kubectldescribe, kubectldelete) that allows attackers to bypass the assertNoDangerousFlags security check by supplying resourceType and name parameters with leading dashes. Attackers can inject the --server flag to redirect kubectl commands to an attacker-controlled API server, causing the operator's bearer token to be transmitted externally and enabling full cluster compromise.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
MCP Server Kubernetesto a version that resolves this vulnerability.Fixed in 3.9.0 - Compensating control
Until upgraded, prevent kubectl commands invoked by MCP Server Kubernetes from accepting attacker-controlled --server (and related dangerous flags), e.g., ensure only trusted inputs are used for resourceType/name parameters so they cannot include leading dashes that bypass assertNoDangerousFlags.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-61459?
The severity of CVE-2026-61459 is rated as critical with a score of 9.8.
What systems are affected by CVE-2026-61459?
CVE-2026-61459 affects MCP Server Kubernetes versions prior to 3.9.0.
How do I fix CVE-2026-61459?
To fix CVE-2026-61459, upgrade MCP Server Kubernetes to version 3.9.0 or later.
What is the nature of the vulnerability in CVE-2026-61459?
CVE-2026-61459 is an argument injection vulnerability that allows attackers to bypass security checks affecting several kubectl structured tools.
Can CVE-2026-61459 be exploited remotely?
Yes, CVE-2026-61459 can be exploited remotely as it allows attackers to use crafted parameters through kubectl commands.