CVE-2026-61459

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-10. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 2.4%CVSS: 9.8Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

MCP Server Kubernetes before 3.9.0 contains an argument injection vulnerability in structured tools (kubectl_get, kubectl_describe, kubectl_delete) that allows attackers to bypass the assertNoDangerousFlags security check by supplying resourceType and name parameters with leading dashes. Attackers can inject the --server flag to redirect kubectl commands to an attacker-controlled API server, causing the operator's bearer token to be transmitted externally and enabling full cluster compromise.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
2.4%
EPSS %ILE
83rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 10, 2026

Last Modified

July 17, 2026

Advisory Details (4)

Auto-updated Oct 10, 2026
Patch available. Sources: github_pr, github_commit.
Web page

MCP Server Kubernetes < 3.9.0 Argument Injection via kubectl Structured Tools | Advisories | VulnCheck

https://www.vulncheck.com/advisories/mcp-server-kubernetes-argument-injection-via-kubectl-structured-tools
GitHub pull request Patch Available

Guard port_forward argv against flag injection

Patch available: Flux159/mcp-server-kubernetes v4.0.0 (PR #329 merged 2026-07-08)

https://github.com/Flux159/mcp-server-kubernetes/pull/329
Web page

kubectl argument injection in structured tools (--server/--token) leaks the operator's cluster bearer token · Issue #328 · Flux159/mcp-server-kubernetes · GitHub

https://github.com/Flux159/mcp-server-kubernetes/issues/328
GitHub commit Patch Available

commit d7890f50a456 (Flux159/mcp-server-kubernetes)

Patch available: Flux159/mcp-server-kubernetes v3.9.0 (contains commit d7890f50a456)

https://github.com/Flux159/mcp-server-kubernetes/commit/d7890f50a4567bf5d9842541ba6f41e180227f9a

Vendor Advisories for CVE-2026-61459(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
mcp-server-kubernetes0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.6
  • every version up to 3.9.0: fixed in 3.9.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 31× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 293 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 193 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 16:33 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  2. 2026-10-14 01:51 UTCEG score recompute
  3. 2026-10-13 16:34 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  4. 2026-10-12 22:05 UTCEG score recompute
  5. 2026-10-12 16:34 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  6. 2026-10-12 15:50 UTCEG score recompute
  7. 2026-10-11 19:34 UTCEG score recompute
  8. 2026-10-11 16:49 UTCEG score recompute
  9. 2026-10-11 14:11 UTCEG score recompute
  10. 2026-10-11 13:49 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  11. 2026-10-10 20:00 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  13. 2026-10-08 17:13 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  15. 2026-10-06 15:18 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  16. 2026-10-05 17:43 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  18. 2026-10-02 17:56 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  19. 2026-10-01 19:50 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  20. 2026-10-01 15:06 UTCEG score recompute
  21. 2026-09-30 15:03 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  22. 2026-09-28 13:51 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  23. 2026-09-28 09:47 UTCEG score recompute
  24. 2026-09-26 15:59 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  25. 2026-09-24 11:10 UTCEG score recompute
Show 75 more
  1. 2026-09-23 17:54 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  2. 2026-09-23 05:45 UTCEG score recompute
  3. 2026-09-18 19:28 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  4. 2026-09-18 05:18 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  6. 2026-09-16 05:15 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  7. 2026-09-13 08:11 UTCEG score recompute
  8. 2026-09-12 02:53 UTCEG score recompute
  9. 2026-09-11 14:53 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  10. 2026-09-11 09:37 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  11. 2026-09-10 09:35 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  12. 2026-09-08 22:01 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  13. 2026-09-08 02:50 UTCEG score recompute
  14. 2026-09-07 16:01 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  15. 2026-09-06 13:57 UTCEG score recompute
  16. 2026-09-06 13:47 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  17. 2026-09-05 21:41 UTCEG score recompute
  18. 2026-09-04 05:07 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  19. 2026-09-02 14:12 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  20. 2026-09-01 13:54 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  21. 2026-09-01 04:40 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  22. 2026-08-30 20:16 UTCEG score recompute
  23. 2026-08-30 19:17 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  24. 2026-08-30 06:24 UTCEG score recompute
  25. 2026-08-30 01:22 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  26. 2026-08-28 21:42 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  27. 2026-08-27 21:40 UTCEG score recompute
  28. 2026-08-27 14:25 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  29. 2026-08-27 00:47 UTCEG score recompute
  30. 2026-08-26 14:46 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  31. 2026-08-25 14:49 UTCEG score recompute
  32. 2026-08-25 13:49 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  33. 2026-08-24 20:14 UTCEG score recompute
  34. 2026-08-24 09:27 UTCEG score recompute
  35. 2026-08-23 01:52 UTCEG score recompute
  36. 2026-08-23 00:19 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  37. 2026-08-22 03:31 UTCEG score recompute
  38. 2026-08-21 23:49 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  39. 2026-08-20 23:42 UTCEG score recompute
  40. 2026-08-20 22:55 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  41. 2026-08-20 01:32 UTCEG score recompute
  42. 2026-08-19 17:04 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  43. 2026-08-18 20:33 UTCEG score recompute
  44. 2026-08-18 13:48 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  45. 2026-08-17 16:07 UTCEG score recompute
  46. 2026-08-17 13:47 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  47. 2026-08-16 17:57 UTCEG score recompute
  48. 2026-08-16 14:56 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  49. 2026-08-16 03:01 UTCEG score recompute
  50. 2026-08-15 04:53 UTCEG score recompute
  51. 2026-08-15 01:30 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  52. 2026-08-13 23:09 UTCEG score recompute
  53. 2026-08-13 22:00 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  54. 2026-08-12 17:25 UTCEG score recompute
  55. 2026-08-12 17:25 UTCGHSA enrichmentGHSA-wmg3-h8mf-wgvr · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-08-12 13:51 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  57. 2026-08-12 13:44 UTCGHSA enrichmentGHSA-wmg3-h8mf-wgvr · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-08-12 10:02 UTCGHSA enrichmentGHSA-wmg3-h8mf-wgvr · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-08-12 06:19 UTCGHSA enrichmentGHSA-wmg3-h8mf-wgvr · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-08-12 02:37 UTCEG score recompute
  61. 2026-08-12 02:37 UTCGHSA enrichmentGHSA-wmg3-h8mf-wgvr · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-08-11 22:56 UTCGHSA enrichmentGHSA-wmg3-h8mf-wgvr · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-08-11 19:15 UTCGHSA enrichmentGHSA-wmg3-h8mf-wgvr · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-08-11 15:34 UTCEG score recompute
  65. 2026-08-11 15:34 UTCGHSA enrichmentGHSA-wmg3-h8mf-wgvr · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-08-11 11:52 UTCGHSA enrichmentGHSA-wmg3-h8mf-wgvr · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-08-11 08:11 UTCGHSA enrichmentGHSA-wmg3-h8mf-wgvr · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-08-11 04:29 UTCGHSA enrichmentGHSA-wmg3-h8mf-wgvr · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-08-11 00:48 UTCEG score recompute
  70. 2026-08-11 00:48 UTCGHSA enrichmentGHSA-wmg3-h8mf-wgvr · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  72. 2026-08-10 21:07 UTCGHSA enrichmentGHSA-wmg3-h8mf-wgvr · GitHub severity CRITICAL · GitHub CVSS 9.8
  73. 2026-08-10 17:26 UTCGHSA enrichmentGHSA-wmg3-h8mf-wgvr · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-08-10 13:45 UTCGHSA enrichmentGHSA-wmg3-h8mf-wgvr · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-08-10 10:04 UTCGHSA enrichmentGHSA-wmg3-h8mf-wgvr · GitHub severity CRITICAL · GitHub CVSS 9.8

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Exploit-DB entry). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-52638
    Published Aug 11, 2026

    mcp-server-kubernetes 3.8.x - Argument Injection

    Open source ↗

Frequently asked(5)

What is CVE-2026-61459?
CVE-2026-61459 is a critical-severity vulnerability; its CVE record was published on July 10, 2026. MCP Server Kubernetes before 3.9.0 contains an argument injection vulnerability in structured tools (kubectlget, kubectldescribe, kubectl_delete) that allows attackers to bypass the assertNoDangerousFlags security check by supplying resourceType and name parameters with leading dashes. Attackers…
When was CVE-2026-61459 made public?
CVE-2026-61459 was made public on July 8, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 10, 2026. EchelonGraph's copy of the record carries a last-modified date of July 17, 2026; the record at its source may have been updated since.
Is CVE-2026-61459 actively exploited?
CVE-2026-61459 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.4% probability of exploitation in the next 30 days (83rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61459?
CVE-2026-61459 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61459?
A fix for CVE-2026-61459 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-61459 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-61459

Explore →

Is Your Infrastructure Affected by CVE-2026-61459?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.