CVE-2025-59376

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:

• Run with --disable-kubectl and/or --disable-helm to fully block those execution paths.
• Put the server behind an allow-list proxy restricting allowed subcommands.

Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command. Typical impact: arbitrary command execution in the application's environment.

CVE-2025-59376 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Kodem intelligence

1. What is CVE-2025-59376? CVE-2025-59376 is a medium-severity command injection vulnerability in mcp-kubernetes-server (pip), affecting versions <= 0.1.11. No fixed version is listed yet. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.
2. How severe is CVE-2025-59376? CVE-2025-59376 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of mcp-kubernetes-server are affected by CVE-2025-59376? mcp-kubernetes-server (pip) versions <= 0.1.11 is affected.
4. Is there a fix for CVE-2025-59376? No fixed version is listed for CVE-2025-59376 yet. Monitor the advisory for updates and apply mitigations in the interim.
5. Is CVE-2025-59376 exploitable, and should I be worried? Whether CVE-2025-59376 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-59376 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-59376? No fixed version is listed yet. In the interim: Avoid constructing commands from untrusted input. Use parameterized APIs that separate the command from its arguments.