CVE-2025-59376Medium· 5.3▾ TwilightPoC availablemcp-kubernetes-server has a Command Injection vulnerability
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 29.2 · likelihood 0.1 · exploitation 12
A public proof-of-concept already exists for this vulnerability — see Exploit availability below.
Public exploit / PoC code seen in 1 source. Availability, not in-the-wild use.
Exploit-prediction probability, daily snapshots since Jul 8.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.3%
0.3% → 0.3%
1 GitHub repo
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 <name>). 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.
Affected versions: through 0.1.11 (no patched release available as of now).
Mitigations:
--disable-kubectl and/or --disable-helm to fully block those execution paths.mcp-kubernetes-server <= 0.1.11Refer to the advisory for the patched release.
Field changes observed since this record was first indexed.