# CVE-2026-129235: Kubeshark: MCP `download_file` writes fetched bytes to an unvalidated destination path

> Attackers influencing Kubeshark MCP download_file arguments can write files anywhere the local user can and read captured network traffic.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **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:** 16 Nov 2026
- **Also known as:** GHSA-gj7r-p794-hhq5

## What is CVE-2026-129235?

CVE-2026-129235 is a medium-severity path traversal 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 download_file tool in cmd/mcpRunner.go accepts caller-controlled path and dest values, fetches a selected Kubeshark Hub API response, and writes the returned bytes through os.Create(dest) in callDownloadFile without confining the destination. An attacker who influences arguments through an AI agent driving kubeshark mcp can write Hub-supplied bytes to any path writable by the local MCP user and can read captured network traffic from default auth-disabled Hub deployments. The tool is registered without --allow-destructive; reliable code execution is not demonstrated because the bytes are constrained to Hub API responses. Hub-side default authentication remains outside this remediation, so captured traffic can remain readable in default auth-disabled Hub deployments after the local destination-write fix. The destination-write 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-129235?

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.20260304171723-eb7dc42b6ea0 | 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-129235?

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

## Is CVE-2026-129235 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-129235 is a medium-severity path traversal 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-129235 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.20260304171723-eb7dc42b6ea0; 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-129235/ (Markdown: https://insights.sbomify.com/CVE-2026-129235/index.md)
```

## Sources

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

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