mcp-kubernetes-server has a Command Injection vulnerability

published 2025-09-15 13 mo ago modified 2026-09-30 39 d ago also GHSA-hjm5-xgj8-vwj6 , PYSEC-2026-1619 , EUVD-2025-29194

cvss: 3.7; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits: 0; none known

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.

CISA SSVC

Exploitation: Proof of concept is public
Automatable: no
Technical impact: partial
Assessed: 13 mo ago (2025-09-15)

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/william31212/CVE-Requests-1896609 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	3.7	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
GitHub	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
OSV	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
pypi	mcp-kubernetes-server	<=0.1.11	no fix listed

Affected products

feiskyer mcp-kubernetes-server

Classification

Weakness

CWE-77 Improper Neutralization of Special Elements used in a Command
CWE-863 Incorrect Authorization

References

github.com /william31212/CVE-Requests-1896609
exploit, web, third-party-advisory
github.com /feiskyer/mcp-kubernetes-server/blob/78957b6c1a3982080cf6fcaac6f6e9014116a71c/src/mcp_kubernetes_server/main.p
web, product
nvd.nist.gov /vuln/detail/CVE-2025-59376
advisory
github.com /feiskyer/mcp-kubernetes-server
package
pypi.org /project/mcp-kubernetes-server
package
github.com /advisories/GHSA-hjm5-xgj8-vwj6
advisory

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary