# mcp-server-kubernetes argument injection can expose Kubernetes cluster credentials Advisory record · `GHSA-wmg3-h8mf-wgvr` - **Identifiers:** `GHSA-wmg3-h8mf-wgvr` · `CVE-2026-61459` · `PYSEC-2026-3685` - **State:** Confirmed - **Severity:** CVSS 9.3 Critical - **Critical:** Yes: CVSS 9+ - **Weakness (CWE):** [CWE-88](https://cwe.mitre.org/data/definitions/88.html) - **Tags:** [Command injection](https://agentprime.io/advisories/tag/command-injection.md) - **Published:** 10 Jul 2026 - **Updated:** 28 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 10 Jul 2026, 21:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Critical Critical, because: - CVSS score 9.3: 9.0 or more. How we decide what’s critical: ## Affected packages - `mcp-server-kubernetes` (npm): affected `<3.9.0`; fixed in `3.9.0` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > mcp-server-kubernetes versions before 3.9.0 are affected by an argument injection flaw in its structured tools kubectl_get, kubectl_describe, and kubectl_delete. The source says that supplying resourceType or name values with leading dashes bypasses the assertNoDangerousFlags check, which lets an attacker add a --server flag that points kubectl at an attacker-controlled API server. This could expose the operator's bearer token and lead to full cluster compromise; the source does not state what access the attacker must already have. Upgrade to mcp-server-kubernetes 3.9.0 or later. Written 31 Oct 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 9.3 Critical, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`, from CNA (VulnCheck) - **CISA KEV:** Not listed. - **EPSS:** 0.024, the 84th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 10 Jul 2026, 18:34 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-61459) - 31 Oct 2026, 13:33 UTC: First seen by agentprime - 31 Oct 2026, 13:33 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-wmg3-h8mf-wgvr) ## Sources - [GitHub Advisory Database: GHSA-wmg3-h8mf-wgvr](https://github.com/advisories/GHSA-wmg3-h8mf-wgvr) - [OSV: GHSA-wmg3-h8mf-wgvr](https://osv.dev/vulnerability/GHSA-wmg3-h8mf-wgvr) - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .