# CVE-2026-129236: Kubeshark: MCP `start_kubeshark` argument injection via `pod_regex` → image redirect → cluster takeover

> Attackers influencing Kubeshark MCP arguments can inject --set pod_regex to redirect privileged images to attacker registries and take over the cluster.

- **Severity:** High 7.2 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** Yes
- **Published:** 16 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-8vf2-hxg5-crqh

## What is CVE-2026-129236?

CVE-2026-129236 is a high-severity command injection vulnerability in kubeshark, published on 16 Nov 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Kubeshark is an eBPF-powered network observability tool for Kubernetes. From 53.1.0 until 53.4.0, the start_kubeshark MCP tool in cmd/mcpRunner.go uses callStartKubeshark to append caller-controlled pod_regex as a bare positional argument to kubeshark tap without a -- end-of-options separator, allowing a value beginning with --set to be parsed as a Helm value override. An attacker who influences tool arguments against kubeshark mcp --allow-destructive can redirect the privileged worker, Hub, and front images through tap.docker.registry and tap.docker.tag to an attacker-controlled registry. Because the deployed worker DaemonSet runs privileged with host networking and host filesystem access, a malicious image can obtain node and cluster-admin access when the host already has permission to deploy it. This issue is fixed in version 53.4.0.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

## Which versions are affected by CVE-2026-129236?

1 open source package ship an affected version, including github.com/kubeshark/kubeshark.

An affected version is exposed as installed. No special setting or call is needed.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `github.com/kubeshark/kubeshark` | Go | `pkg:golang/github.com/kubeshark/kubeshark` | From 0.0.2-0.20260206182249-0bbbb473ea3f | 0.0.2-0.20260812200004-a76a1920dc75 |

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| Upstream |  | fixed | `github.com/kubeshark/kubeshark` | 0.0.2-0.20260812200004-a76a1920dc75 |

## How do I fix CVE-2026-129236?

Upgrade github.com/kubeshark/kubeshark to 0.0.2-0.20260812200004-a76a1920dc75 or later.

## Is CVE-2026-129236 being exploited?

There is no known exploitation of CVE-2026-129236 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129236 and fix it if it is affected.

What it is: CVE-2026-129236 is a high-severity command injection vulnerability in kubeshark, published on 16 Nov 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-129236 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected packages and fixed versions:
- github.com/kubeshark/kubeshark (Go): affected from 0.0.2-0.20260206182249-0bbbb473ea3f; fixed in 0.0.2-0.20260812200004-a76a1920dc75

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-129236/ (Markdown: https://insights.sbomify.com/CVE-2026-129236/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129236
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129236
- OSV: https://osv.dev/vulnerability/CVE-2026-129236

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129236/
Summaries are generated and may contain mistakes; the official description above is the record.
