{"id":"CVE-2025-59376","aliases":["EUVD-2025-29194","GHSA-hjm5-xgj8-vwj6","PYSEC-2026-1619"],"status":"published","title":"mcp-kubernetes-server has a Command Injection vulnerability","description":"feiskyer mcp-kubernetes-server through 0.1.11 does not consider chained commands in the implementation of --disable-write and --disable-delete, e.g., it allows a \"kubectl version; kubectl delete pod\" command because the first word (i.e., \"version\") is not a write or delete operation.","severity":{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"low","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.00302,"percentile":0.23134,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":true,"fix_available":false},"cwes":["CWE-77","CWE-863"],"published":"2025-09-15T00:00:00Z","modified":"2026-10-28T02:30:37Z","exploits":[{"source":"pocgithub","id":"william31212/CVE-Requests-1896609","title":"william31212/CVE-Requests-1896609","date":"2025-09-15","url":"https://github.com/william31212/CVE-Requests-1896609"}],"affected":[{"source":"ghsa","ecosystem":"PyPI","package":"mcp-kubernetes-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"0.1.11"}]}]},{"source":"osv","ecosystem":"PyPI","package":"mcp-kubernetes-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"0.1.11"}]}],"versions":["0.1.0","0.1.1","0.1.10","0.1.11","0.1.2","0.1.3","0.1.4","0.1.5","0.1.6","0.1.7","0.1.8","0.1.9"]},{"source":"osv","ecosystem":"PyPI","package":"mcp-kubernetes-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"0.1.11"}]}],"versions":["0.1.0","0.1.1","0.1.10","0.1.11","0.1.2","0.1.3","0.1.4","0.1.5","0.1.6","0.1.7","0.1.8","0.1.9"]}],"products":[{"vendor":"feisky","product":"mcp-kubernetes-server"},{"vendor":"feiskyer","product":"mcp-kubernetes-server"}],"references":[{"url":"https://github.com/feiskyer/mcp-kubernetes-server/blob/78957b6c1a3982080cf6fcaac6f6e9014116a71c/src/mcp_kubernetes_server/main.py#L106-L137","tags":["Product","web"]},{"url":"https://github.com/william31212/CVE-Requests-1896609","tags":["exploit","Third Party Advisory","package","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-59376","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-hjm5-xgj8-vwj6","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/59xxx/CVE-2025-59376.json","tags":["advisory"]},{"url":"https://github.com/feiskyer/mcp-kubernetes-server","tags":["package"]},{"url":"https://pypi.org/project/mcp-kubernetes-server","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2025-59376","description":"feiskyer mcp-kubernetes-server through 0.1.11 does not consider chained commands in the implementation of --disable-write and --disable-delete, e.g., it allows a \"kubectl version; kubectl delete pod\" command because the first word (i.e., \"version\") is not a write or delete operation.","status":"published","published":"2025-09-15T00:00:00Z","modified":"2025-09-15T15:10:46.266Z","cvss":[{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"low","assessor":"cna"}],"cwes":["CWE-77"],"updated_at":"2026-11-02T14:32:47.812946Z"}],"euvd":[{"id":"EUVD-2025-29194","description":"feiskyer mcp-kubernetes-server through 0.1.11 does not consider chained commands in the implementation of --disable-write and --disable-delete, e.g., it allows a \"kubectl version; kubectl delete pod\" command because the first word (i.e., \"version\") is not a write or delete operation.","status":"published","published":"2025-09-15T00:00:00Z","modified":"2025-09-15T15:10:46Z","cvss":[{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"low"}],"updated_at":"2026-11-02T20:31:44.034664Z"}],"ghsa":[{"id":"GHSA-hjm5-xgj8-vwj6","title":"mcp-kubernetes-server has a Command Injection vulnerability","description":"`mcp-kubernetes-server` does not correctly enforce the `--disable-write` / `--disable-delete` protections when commands are chained. The server only inspects the first token to decide whether an operation is write/delete, which allows a read-like command to be followed by a write action using shell metacharacters (e.g., `kubectl version; kubectl delete pod \u003cname\u003e`). A remote attacker who can invoke the server may therefore bypass the intended write/delete restrictions and perform state-changing operations against the Kubernetes cluster.\n\n**Affected versions:** through `0.1.11` (no patched release available as of now).\n\n**Mitigations:**\n- Run with `--disable-kubectl` and/or `--disable-helm` to fully block those execution paths.\n- Put the server behind an allow-list proxy restricting allowed subcommands.","status":"published","published":"2025-09-15T15:31:24Z","modified":"2025-09-25T20:35:22Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"medium"}],"cwes":["CWE-77"],"updated_at":"2026-11-02T14:38:58.965005Z"}],"nvd":[{"id":"CVE-2025-59376","description":"feiskyer mcp-kubernetes-server through 0.1.11 does not consider chained commands in the implementation of --disable-write and --disable-delete, e.g., it allows a \"kubectl version; kubectl delete pod\" command because the first word (i.e., \"version\") is not a write or delete operation.","status":"published","published":"2025-09-15T14:15:44.087Z","modified":"2026-09-30T23:10:00.237Z","cvss":[{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"low","assessor":"secondary"},{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"medium","assessor":"primary"}],"cwes":["CWE-77","CWE-863"],"updated_at":"2026-11-02T14:11:29.650057Z"}],"osv":[{"id":"CVE-2025-59376","description":"feiskyer mcp-kubernetes-server through 0.1.11 does not consider chained commands in the implementation of --disable-write and --disable-delete, e.g., it allows a \"kubectl version; kubectl delete pod\" command because the first word (i.e., \"version\") is not a write or delete operation.","status":"published","published":"2025-09-15T00:00:00Z","modified":"2026-10-28T02:30:37.244545328Z","cvss":[{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"low"}],"cwes":["CWE-77"],"updated_at":"2026-11-02T15:44:51.190588Z"},{"id":"GHSA-hjm5-xgj8-vwj6","title":"mcp-kubernetes-server has a Command Injection vulnerability","description":"`mcp-kubernetes-server` does not correctly enforce the `--disable-write` / `--disable-delete` protections when commands are chained. The server only inspects the first token to decide whether an operation is write/delete, which allows a read-like command to be followed by a write action using shell metacharacters (e.g., `kubectl version; kubectl delete pod \u003cname\u003e`). A remote attacker who can invoke the server may therefore bypass the intended write/delete restrictions and perform state-changing operations against the Kubernetes cluster.\n\n**Affected versions:** through `0.1.11` (no patched release available as of now).\n\n**Mitigations:**\n- Run with `--disable-kubectl` and/or `--disable-helm` to fully block those execution paths.\n- Put the server behind an allow-list proxy restricting allowed subcommands.","status":"published","published":"2025-09-15T15:31:24Z","modified":"2026-07-07T17:57:11.934816555Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"medium"}],"cwes":["CWE-77"],"updated_at":"2026-11-02T15:46:49.28217Z"},{"id":"PYSEC-2026-1619","title":"mcp-kubernetes-server has a Command Injection vulnerability","description":"`mcp-kubernetes-server` does not correctly enforce the `--disable-write` / `--disable-delete` protections when commands are chained. The server only inspects the first token to decide whether an operation is write/delete, which allows a read-like command to be followed by a write action using shell metacharacters (e.g., `kubectl version; kubectl delete pod \u003cname\u003e`). A remote attacker who can invoke the server may therefore bypass the intended write/delete restrictions and perform state-changing operations against the Kubernetes cluster.\n\n**Affected versions:** through `0.1.11` (no patched release available as of now).\n\n**Mitigations:**\n- Run with `--disable-kubectl` and/or `--disable-helm` to fully block those execution paths.\n- Put the server behind an allow-list proxy restricting allowed subcommands.","status":"published","published":"2026-07-07T16:03:05.120447Z","modified":"2026-07-07T17:47:03.424682277Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T15:52:55.06457Z"}]}}