← Back
CVE-2026-61459
critical
CVSS 9.8
Vulnerability in mcp-server-kubernetes (CVE-2026-61459)
Summary
vulnerability in mcp-server-kubernetes (CVE-2026-61459). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `3.9.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-61459** has been found in mcp-server-kubernetes.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade mcp-server-kubernetes to **3.9.0** or later.
If unsure, ask your IT team or search "mcp-server-kubernetes CVE-2026-61459" on the vendor's site.
CVE-2026-61459 (mcp-server-kubernetes) — CWE-88 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `3.9.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.
❓ What is the problem
**A vulnerability** (CWE-88) exists in mcp-server-kubernetes.
📍 Affected scope
mcp-server-kubernetes — .
🔥 Severity
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **3.9.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade mcp-server-kubernetes to 3.9.0ステージング環境で 3.9.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
mcp-server-kubernetes
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.9.0"}]}]
References
- web https://github.com/Flux159/mcp-server-kubernetes/commit/d7890f50a4567bf5d9842541ba6f41e180227f9a
- web https://github.com/Flux159/mcp-server-kubernetes/issues/328
- web https://github.com/Flux159/mcp-server-kubernetes/pull/329
- web https://github.com/Flux159/mcp-server-kubernetes/releases/tag/3.9.0
- web https://www.vulncheck.com/advisories/mcp-server-kubernetes-argument-injection-via-kubectl-structured-tools
- web https://nvd.nist.gov/vuln/detail/CVE-2026-61459
- web https://github.com/advisories/GHSA-wmg3-h8mf-wgvr