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

Medium 5.3 Published Updated

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

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

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

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.

PackageAffectedFixed in
github.com/kubeshark/kubeshark Go
pkg:golang/github.com/kubeshark/kubeshark
From 0.0.2-0.20260304171723-eb7dc42b6ea00.0.2-0.20260812200004-a76a1920dc75
Status by vendor (1)
WhoReleaseStatusPackages
Upstreamfixedgithub.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.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2026-129235 being exploited?

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

Sources

Also known as GHSA-gj7r-p794-hhq5.

Is CVE-2026-129235 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free