Vulnerability in mcp-server-kubernetes (CVE-2026-47250)
Summary
Vulnerability in mcp-server-kubernetes (CVE-2026-47250). Confidential information can be exposed externally. Exploitable via kubectl_generic. Mitigation: upgrade to 3.7.0 or later.
Original description
The description as published by the source.
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 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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47250 has been found in mcp-server-kubernetes.
Attackers can target a specific entry point like kubectl_generic over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.1/10.
What to do: upgrade mcp-server-kubernetes to 3.7.0 or later.
If unsure, ask your IT team or search "mcp-server-kubernetes CVE-2026-47250" on the vendor's site.
CVE-2026-47250 (mcp-server-kubernetes) — CWE-88 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: kubectl_generic / flags / args / openssl
Patched: 3.7.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-88) exists in mcp-server-kubernetes. Attackers reach the vulnerable code path via kubectl_generic without authentication.
Check the vendor advisory for the affected versions of mcp-server-kubernetes. Attack surface: kubectl_generic / flags / args / openssl.
Severity: Medium (CVSS 6.1/10). Confidential information can be exposed externally.
Update to 3.7.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mcp-server-kubernetes' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mcp-server-kubernetes' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mcp-server-kubernetesを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade mcp-server-kubernetes to 3.7.0ステージング環境で 3.7.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com