Argument Injection Vulnerability (CVE‑2026‑61459) in mcp‑server‑kubernetes 3.8.x Enables Bearer‑Token Exfiltration

Argument Injection Vulnerability (CVE‑2026‑61459) in mcp‑server‑kubernetes 3.8.x Enables Bearer‑Token Exfiltration

What Happened – A remote‑code argument injection flaw (CVE‑2026‑61459) was disclosed for mcp‑server‑kubernetes versions < 3.9.0. The defect allows an attacker to inject arbitrary --server arguments into the kubectl_get, kubectl_describe, and kubectl_delete utilities, causing the Kubernetes API server URL to be overwritten and the bearer token to be sent to an attacker‑controlled endpoint.

Why It Matters for Compliance & Audit Readiness

• The vulnerability directly subverts SOC 2 CC6.1 (Logical Access Control) by allowing unauthorized extraction of privileged credentials.
• Continuous‑compliance programs must demonstrate that argument‑validation controls are in place and that any deviation is logged and auditable – exactly the evidence Verisq’s Control‑Mapping capability can capture.
• Failure to remediate can break the Security principle of the Trust Services Criteria, exposing organizations to audit findings and loss of attestation credibility.

Who Is Affected – Cloud‑infrastructure operators, SaaS platforms, and any organization that runs the open‑source mcp‑server‑kubernetes component in production (primarily CLOUD_INFRA and TECH_SAAS sectors).

Recommended Actions

• Upgrade immediately to mcp‑server‑kubernetes 3.9.0 or later.
• Validate that all client‑side tools sanitize arguments; map this requirement to SOC 2 CC6.1 and capture remediation evidence in your control repository.
• Rotate any bearer tokens that may have been exposed and enforce short‑lived token policies.
• Enable continuous monitoring of command‑line inputs and audit logs for anomalous --server parameters.

Source: Exploit‑DB #52638

Technical Notes – The flaw is an Argument Injection (remote) affecting the JSON‑RPC endpoint of the MCP server. CVSS 9.3 (Critical). Exploit requires network access to the MCP server and the ability to invoke the vulnerable tools. Successful exploitation leaks the Authorization header containing the Kubernetes bearer token.