← Back
CVE-2026-46519
high
CVSS 8.8
Authorization Flaw in mcp-server-kubernetes (CVE-2026-46519)
Summary
vulnerability in mcp-server-kubernetes (CVE-2026-46519). Successful exploitation can lead to full system takeover. Exploitable via ``ALLOW_ONLY_READONLY_TOOLS``. Mitigation: upgrade to `3.6.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-46519** has been found in mcp-server-kubernetes.
Attackers can target a specific entry point like ``ALLOW_ONLY_READONLY_TOOLS`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade mcp-server-kubernetes to **3.6.0** or later.
If unsure, ask your IT team or search "mcp-server-kubernetes CVE-2026-46519" on the vendor's site.
CVE-2026-46519 (mcp-server-kubernetes) — CWE-863 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `ALLOW_ONLY_READONLY_TOOLS` / `ALLOW_ONLY_NON_DESTRUCTIVE_TOOLS` / `ALLOWED_TOOLS` / `kubectl_delete`
Patched: `3.6.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
**incorrect authorization** (CWE-863) exists in mcp-server-kubernetes. Attackers reach the vulnerable code path via ``ALLOW_ONLY_READONLY_TOOLS`` without authentication.
📍 Affected scope
mcp-server-kubernetes — . Attack surface: `ALLOW_ONLY_READONLY_TOOLS` / `ALLOW_ONLY_NON_DESTRUCTIVE_TOOLS` / `ALLOWED_TOOLS` / `kubectl_delete`.
🔥 Severity
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **3.6.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.6.0ステージング環境で 3.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
mcp-server-kubernetes
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.6.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-46519
- package https://github.com/Flux159/mcp-server-kubernetes
- web https://github.com/Flux159/mcp-server-kubernetes/security/advisories/GHSA-cr22-wjx7-2w6m
- web https://github.com/advisories/GHSA-cr22-wjx7-2w6m
- web https://github.com/Flux159/mcp-server-kubernetes/releases/tag/v3.6.0