PYSEC-2026-1619

Vulnerability from pysec - Published: 2026-07-07 16:03 - Updated: 2026-07-07 17:24
VLAI
Details

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.

Impacted products
Name purl
mcp-kubernetes-server pkg:pypi/mcp-kubernetes-server

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "mcp-kubernetes-server",
        "purl": "pkg:pypi/mcp-kubernetes-server"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "last_affected": "0.1.11"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "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"
      ]
    }
  ],
  "aliases": [
    "CVE-2025-59376",
    "GHSA-hjm5-xgj8-vwj6"
  ],
  "details": "`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.",
  "id": "PYSEC-2026-1619",
  "modified": "2026-07-07T17:24:39.811168Z",
  "published": "2026-07-07T16:03:05.120447Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-59376"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/feiskyer/mcp-kubernetes-server"
    },
    {
      "type": "WEB",
      "url": "https://github.com/feiskyer/mcp-kubernetes-server/blob/78957b6c1a3982080cf6fcaac6f6e9014116a71c/src/mcp_kubernetes_server/main.py#L106-L137"
    },
    {
      "type": "WEB",
      "url": "https://github.com/william31212/CVE-Requests-1896609"
    },
    {
      "type": "PACKAGE",
      "url": "https://pypi.org/project/mcp-kubernetes-server"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-hjm5-xgj8-vwj6"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "mcp-kubernetes-server has a Command Injection vulnerability"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…