CVE-2026-61459 Flux159 CVE debrief

Who should care

Users of MCP Server Kubernetes before version 3.9.0 should assess their exposure and apply patches or mitigations as available. This includes operators, platform administrators, vulnerability management teams, and security teams who need to review compensating controls for exposed systems while remediation is scheduled and verified.

Technical summary

The MCP Server Kubernetes application, prior to version 3.9.0, contains an argument injection vulnerability in its structured tools, specifically kubectl_get, kubectl_describe, and kubectl_delete. This vulnerability allows attackers to bypass the assertNoDangerousFlags security check by providing resourceType and name parameters with leading dashes. By exploiting this, attackers can inject the --server flag, redirecting kubectl commands to an attacker-controlled API server. This redirection causes the operator's bearer token to be transmitted externally, potentially enabling full cluster compromise.

Defensive priority

High priority should be given to updating MCP Server Kubernetes to version 3.9.0 or later. In the interim, users should closely monitor and restrict the use of kubectl commands, especially in environments where the --server flag can be controlled by user input.

Recommended defensive actions

• Update MCP Server Kubernetes to version 3.9.0 or later
• Restrict and monitor kubectl command usage
• Implement additional security measures to protect against unauthorized API server access
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. Additional information can be found in the referenced GitHub commits, issues, and releases, as well as the Vulncheck advisories. The vulnerability allows attackers to bypass the assertNoDangerousFlags security check by supplying resourceType and name parameters with leading dashes. This could potentially enable full cluster compromise if an attacker-controlled API server is used. Users should verify their exposure and review the official advisory for affected scope and severity. Defenders should check relevant monitoring, detection, and logs for exposed assets that need extra review.

Official resources