Skip to main content
Menu
CVEs

CVE

Kubeshark cluster takeover via argument injection in MCP tool

CVE-2026-129236

CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H

7.2HighCNA
Exploited
No known exploitation
Fix
Fixed in 53.4.0
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Affected versions are 53.1.0 up to but not including 53.4.0. The MCP start_kubeshark tool is only registered when kubeshark mcp is run with --allow-destructive.

Published
Last modified
Reference
Last checked
12/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

Kubeshark, a network observability tool for Kubernetes, has a flaw in its start_kubeshark tool. An attacker with local access, high privileges, and a user action can inject arguments that redirect its worker, Hub, and front images to an attacker-controlled registry, and a malicious image can then gain node and cluster-admin access where the host already has permission to deploy it.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

Kubeshark is an eBPF-powered network observability tool for Kubernetes. From 53.1.0 until 53.4.0, the start_kubeshark MCP tool in cmd/mcpRunner.go uses callStartKubeshark to append caller-controlled pod_regex as a bare positional argument to kubeshark tap without a -- end-of-options separator, allowing a value beginning with --set to be parsed as a Helm value override. An attacker who influences tool arguments against kubeshark mcp --allow-destructive can redirect the privileged worker, Hub, and front images through tap.docker.registry and tap.docker.tag to an attacker-controlled registry. Because the deployed worker DaemonSet runs privileged with host networking and host filesystem access, a malicious image can obtain node and cluster-admin access when the host already has permission to deploy it. This issue is fixed in version 53.4.0.

Who should check

Teams running the kubeshark CLI's MCP server (kubeshark mcp --allow-destructive) on versions 53.1.0 up to 53.4.0, especially hosts with kubeconfigs that can deploy privileged DaemonSets.

“Affected versions: >= v53.1.0 , < v53.4.0”

github.com

cve.now Index

12Pcve.now Index 12 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.2/10CVSS 7.2
  • No patch0/5No signal

What would change the score

  • Would score about 62 if added to CISA KEV
  • Would score about 57 if CISA's SSVC rates exploitation active
  • Would score about 22 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Affected versions are 53.1.0 up to but not including 53.4.0. The MCP start_kubeshark tool is only registered when kubeshark mcp is run with --allow-destructive.
  • Upgrade to a fixed version: 53.4.0.

  • Workaround: Do not run kubeshark mcp with --allow-destructive unless required.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129236 (Kubeshark: MCP `start_kubeshark` argument injection via `pod_regex` → image redirect → cluster takeover), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129236 (entry last updated 2026-11-16):
Affected:
- kubeshark kubeshark: from 53.1.0, fixed in 53.4.0
Fixed versions: 53.4.0.
Conditions (all must be true for the bug to be hit):
- Affected versions are 53.1.0 up to but not including 53.4.0. (source: https://github.com/kubeshark/kubeshark/security/advisories/GHSA-8vf2-hxg5-crqh)
- The MCP start_kubeshark tool is only registered when kubeshark mcp is run with --allow-destructive. (source: https://github.com/kubeshark/kubeshark/security/advisories/GHSA-8vf2-hxg5-crqh)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: local access, high-privilege login, a user action.
Workaround: Do not run kubeshark mcp with --allow-destructive unless required. (source: https://github.com/kubeshark/kubeshark/security/advisories/GHSA-8vf2-hxg5-crqh)
CISA KEV: CVE-2026-129236 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129236 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/kubeshark/kubeshark/security/advisories/GHSA-8vf2-hxg5-crqh
- https://github.com/kubeshark/kubeshark/pull/1957
- https://github.com/kubeshark/kubeshark/commit/a76a1920dc7587be700a17f1592f58a9512ad214
- https://github.com/kubeshark/kubeshark/releases/tag/v53.4.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129236
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129236"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • kubeshark kubeshark

    From 53.1.0 · fixed in 53.4.0

Evidence 6

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 3

  1. Repository
  2. Repository
  3. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129236

Is CVE-2026-129236 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The MCP start_kubeshark tool accepts a pod_regex argument that is not properly validated, so a single injected argument can redirect the privileged worker, hub and front images to an attacker-controlled registry. The advisory says this can lead to full cluster compromise with cluster-admin rights.Source: github.com

Which versions are affected by CVE-2026-129236?

kubeshark: from 53.1.0 before 53.4.0.Source: cve.now feed data

Am I affected, and how do I check?

Versions 53.1.0 up to but not including 53.4.0 of kubeshark are affected. The tool is only registered when kubeshark mcp is run with the --allow-destructive flag, so check whether that flag is used in your setup and which kubeshark version is installed.Source: github.com

How do I fix CVE-2026-129236?

Upgrade kubeshark to version 53.4.0, which is the fixed version listed for this vulnerability. Until the upgrade is done, the advisory's workaround is to avoid running kubeshark mcp with --allow-destructive unless it is required.Source: github.com