Skip to main content
VulnerabilityPublished

CVE-2026-129235: kubeshark · Argument Injection

Affects kubesharkSource CVE Database V5

0
Compare

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

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
kubesharkkubesharkAffected
  • >=53.1.0 <53.4.0
Fixed in
  • 53.4.0

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

Community reviews

Loading reviews…