VYPR
Moderate severityNVD Advisory· Published Sep 15, 2025· Updated Sep 15, 2025

CVE-2025-59376

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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

feiskyer mcp-kubernetes-server <=0.1.11 fails to block chained commands, allowing bypass of write/delete restrictions via shell metacharacters.

Vulnerability

Overview

The feiskyer mcp-kubernetes-server, an MCP server enabling AI assistants to interact with Kubernetes clusters, contains a validation flaw in its kubectl tool. The server constructs shell commands by prepending "kubectl" to user input, but only inspects the first word of the command to enforce safety flags like --disable-write and --disable-delete. This allows chaining commands using shell metacharacters such as ; [1][3]. For example, a command like kubectl version; kubectl delete pod is permitted because the first word "version" is not a write or delete operation, bypassing the intended restrictions [1].

Exploitation

An attacker with access to the MCP server (e.g., through an AI assistant or directly) can craft input that includes multiple commands separated by shell metacharacters. The server does not sanitize or prevent such chaining, enabling the execution of arbitrary kubectl commands even when write or delete operations are explicitly disallowed [1]. The same technique also leads to OS command injection (CWE-78) because the entire user input is passed to a shell [1].

Impact

Successful exploitation allows an attacker to perform destructive actions like deleting pods or modifying deployments despite --disable-delete or --disable-write being active. Combined with the command injection vector, this can lead to remote code execution on the host running the MCP server, potentially compromising both the host and the connected Kubernetes cluster [1][2].

Mitigation

As of the latest available information, the issue affects all versions up to and including 0.1.11, and no patched version has been released [1][3]. Users should restrict access to the MCP server, apply network segmentation, and monitor for unusual command patterns until an official fix is available.

AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
mcp-kubernetes-serverPyPI
<= 0.1.11

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

3

News mentions

0

No linked articles in our index yet.