Skip to main content
VulnerabilityPublished

CVE-2026-129236: kubeshark · Argument Injection

Affects kubesharkSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.2 High : upgrade to 53.4.0 soon.

Data as of 16 Nov 2026, 17:19 UTC

CVSS 3.1 base score
7.2High
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.17.2
Patch
Available – fixed in 53.4.0
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H

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 this vulnerability is fixed. No other mitigations are indicated by the vendor advisory. Ensure that only trusted users can influence the pod_regex argument to prevent exploitation.

Description

CVE-2026-129236 is an argument injection vulnerability in kubeshark versions 53.1.0 through 53.3.0. The vulnerability arises because the start_kubeshark MCP tool appends a caller-controlled pod_regex argument without an end-of-options separator, allowing specially crafted input to be interpreted as Helm value overrides. This can lead to redirecting privileged container images to attacker-controlled registries. Since the worker DaemonSet runs with privileged host networking and filesystem access, exploitation can result in node and cluster-admin level access. The issue is fixed in version 53.4.0.

References

Community reviews

Loading reviews…