CVE-2026-61459: CVE-2026-61459: MCP Server Kubernetes before 3.9.0 contains an argument injection vulnerability in structu…
suyogs · mcp-server-kubernetes · NVD published 2026-07-11 · posted 2026-08-11 · last modified 2026-07-17
What it is
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.
| Weakness | CWE-88 |
|---|---|
| CVSS vector | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X (source: [email protected]) |
| ATT&CK tactics | n/a |
Exploitation evidence
First exploit evidence seen: 2026-08-11 (earliest date across the sources below).
Exploited in the wild
No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).
Public exploit code
Exploit-DB
- EDB-52638: mcp-server-kubernetes 3.8.x - Argument Injection (2026-08-11)
Sources: Exploit-DB (OffSec).
No ATT&CK techniques could be mapped or inferred for this CVE yet.
How to fix it
Fixed versions
- suyogs mcp-server-kubernetes: upgrade to 3.9.0 or later
Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.
Vendor advisories and patches
- https://github.com/Flux159/mcp-server-kubernetes/commit/d7890f50a4567bf5d9842541ba6f41e180227f9a (Patch)
- https://github.com/Flux159/mcp-server-kubernetes/issues/328 (Issue Tracking, Exploit, Mitigation, Vendor Advisory)
- https://github.com/Flux159/mcp-server-kubernetes/pull/329 (Issue Tracking, Patch)
- https://github.com/Flux159/mcp-server-kubernetes/releases/tag/3.9.0 (Release Notes)
Detection Generic guidance
Response checklist Generic guidance
- Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
- Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
- Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
- Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.