github.com/kubeshark/kubeshark · Kubeshark: MCP `start_kubeshark` argument injection via `pod_regex` → image redirect → cluster takeover
Affects github.com/kubeshark/kubesharkSource GCVE Database
Not known to be exploited · CVSS 7.2 High : upgrade to 0.0.2-0.20260812200004-a76a1920dc75 soon.
Data as of 17 Nov 2026, 00:03 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.2 |
|---|
- Patch
- Available – fixed in 0.0.2-0.20260812200004-a76a1920dc75
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade github.com/kubeshark/kubeshark to 0.0.2-0.20260812200004-a76a1920dc75.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Gogithub.com/kubeshark/kubeshark | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in kubeshark version v53.4.0 that fixes the argument injection by adding an end-of-options separator before the pod_regex argument. Users should upgrade to v53.4.0 or later. Until patched, do not run kubeshark mcp with the --allow-destructive flag unless necessary, avoid exposing the MCP server to untrusted inputs, and restrict kubeconfig permissions on hosts running the MCP server to limit potential impact.
Description
A command injection vulnerability exists in the kubeshark MCP tool's start_kubeshark command due to improper handling of the pod_regex argument. This flaw allows an attacker with local access and certain privileges to inject arbitrary Helm --set flags, redirecting container images to attacker-controlled registries. The deployed containers run privileged with host network and filesystem access, enabling full Kubernetes cluster takeover. The vulnerability affects versions from v53.1.0 up to but not including v53.4.0 and is fixed in v53.4.0.
References
- github.com/kubeshark/kubeshark/security/advisories/GHSA-8vf2-hxg5-crqh (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-129236 (opens in a new tab)
- github.com/kubeshark/kubeshark/pull/1957 (opens in a new tab)
- github.com/kubeshark/kubeshark/commit/a76a1920dc7587be700a17f1592f58a9512ad214 (opens in a new tab)
- github.com/kubeshark/kubeshark (opens in a new tab)
- github.com/kubeshark/kubeshark/releases/tag/v53.4.0 (opens in a new tab)