MCP Server Kubernetes < 3.9.0 Argument Injection via kubectl Structured Tools
Flux159 mcp-server-kubernetes
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| mcp-server-kubernetes npm |
|
|
| mcp-server-kubernetes PyPI |
|
|
Flux159 mcp-server-kubernetes
| Product | Affected | Fixed in |
|---|---|---|
| mcp-server-kubernetes npm |
|
|
| mcp-server-kubernetes PyPI |
|
|
MCP Server Kubernetes before 3.9.0 contains an argument injection vulnerability in structured tools (kubectl_get, kubectl_describe, kubectl_delete) 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.
From the CVE record · VulnCheck
Before 3.9.0, the structured kubectl_get, kubectl_describe, and kubectl_delete tools allow argument injection through resourceType and name parameters that start with dashes. An attacker who can supply those parameters can bypass the dangerous-flag check and redirect kubectl to an attacker-controlled API server, exposing the operator's bearer token and potentially enabling full cluster compromise.
Teams running the npm or PyPI mcp-server-kubernetes package before 3.9.0 should check their deployments.