How severe is CVE-2026-61459?

No CVSS score has been assigned to CVE-2026-61459 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-61459?

CVE-2026-61459 affects the following packages: mcp-server-kubernetes (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-61459?

Update mcp-server-kubernetes to 3.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-61459 is resolved across your whole dependency graph.

How do I detect CVE-2026-61459 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mcp-server-kubernetes, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-61459 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-61459 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2026-61459, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2026-61459?

CVE-2026-61459 has an EPSS (Exploit Prediction Scoring System) score of 2.4%, placing it in the 83th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-61459?

CVE-2026-61459 is classified as CWE-88 (CWE-88). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-61459 published, and has it been updated?

CVE-2026-61459 was published on July 10, 2026 and was last updated on August 19, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2026-61459 — mcp-server-kubernetes

Fix: Flux159/mcp-server-kubernetes@d7890f5

CVE-2026-61459 is a CWE-88 vulnerability in mcp-server-kubernetes. 1 public exploit reference exists, so weaponization risk is real. A fix is available for mcp-server-kubernetes — see the affected versions and patch details below.

MCP Server Kubernetes < 3.9.0 Argument Injection via kubectl Structured Tools

Also known asGHSA-wmg3-h8mf-wgvrPYSEC-2026-3685

Published

Jul 10, 2026

Updated

Aug 19, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Oct 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-61459.

EPSS Exploitation Probability

via FIRST.org ↗

2.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍mcp-server-kubernetes

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`mcp-server-kubernetes`	all versions	3.9.0`pip install --upgrade 'mcp-server-kubernetes==3.9.0'`

Affected Products

1 product · 1 configurations

Application

mcp-server-kubernetessuyogs

< 3.9.0

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52638remotemultiple

mcp-server-kubernetes 3.8.x - Argument Injection

by banyamer · Aug 11, 2026

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mcp-server-kubernetes, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mcp-server-kubernetes to 3.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-61459 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-61459 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works