CVE-2026-129235: kubeshark · Argument Injection
Affects kubesharkSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 53.4.0 when convenient.
Data as of 16 Nov 2026, 17:19 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.3 |
|---|
- Patch
- Available – fixed in 53.4.0
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 15 Nov 2026.
What to do
Upgrade kubeshark to 53.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| kubesharkkubeshark | Affected
| Fixed in
|
AI-suggested
Upgrade Kubeshark to version 53.4.0 or later, where the destination-write vulnerability in the download_file tool is fixed. Additionally, enable authentication on the Kubeshark Hub to prevent unauthorized reading of captured network traffic, as this remains outside the scope of the local destination-write fix.
Description
Kubeshark versions from 53.1.0 up to but not including 53.4.0 contain an argument injection vulnerability in the download_file tool. This flaw allows an attacker who can influence arguments via an AI agent driving kubeshark mcp to write bytes fetched from the Kubeshark Hub API to any writable path by the local MCP user. Although reliable code execution is not demonstrated, the vulnerability can lead to unauthorized writing of data. The issue is fixed in version 53.4.0. Default authentication remains disabled by default on the Hub side, so captured network traffic may still be readable despite the fix for the local destination-write problem.
References
- github.com/kubeshark/kubeshark/security/advisories/GHSA-gj7r-p794-hhq5 (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/releases/tag/v53.4.0 (opens in a new tab)