CVE-2026-129235: Kubeshark · MCP `download_file` writes fetched bytes to an unvalidated destination path
Affects github.com/kubeshark/kubesharkSource GCVE Database
Not known to be exploited · CVSS 5.3 Medium : upgrade to 0.0.2-0.20260812200004-a76a1920dc75 when convenient.
Data as of 17 Nov 2026, 00:04 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.3 |
|---|
- Patch
- Available – fixed in 0.0.2-0.20260812200004-a76a1920dc75
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:NExploitation 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
Upgrade to Kubeshark version v53.4.0 or later, where the vulnerability is fixed. The patch validates and sanitizes the destination path to prevent arbitrary file writes. Additionally, enable Hub authentication to prevent unauthorized access to sensitive captured traffic data, as the default community installation ships with authentication disabled. No other immediate actions are required.
Description
Kubeshark MCP tool 'download_file' versions from v53.1.0 up to v53.3.0 allow an attacker who can influence MCP tool arguments to write arbitrary files to any writable path on the local filesystem without validation. The tool fetches data from any Hub API endpoint and writes it to a user-supplied destination path without sanitization, enabling arbitrary file write as the MCP user. On default community installs where Hub authentication is disabled, sensitive captured traffic data including credentials can be read and exfiltrated. The issue is fixed in v53.4.0.
References
- github.com/kubeshark/kubeshark/security/advisories/GHSA-gj7r-p794-hhq5 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-129235 (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)