PT-2026-148335
CVE-2026-129236
·
Published
2026-11-16
·
Updated
2026-11-17
Description by
CVSS 3.1
7.2
HighMetricsAV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H
Name of the Vulnerable Software and Affected Versions
Kubeshark versions 53.1.0 through 53.3.0
Description
The
start kubeshark MCP tool in cmd/mcpRunner.go fails to use an end-of-options separator when appending the pod regex variable to the kubeshark tap command. This allows a value starting with --set to be interpreted as a Helm value override rather than a positional argument. An attacker who can influence tool arguments—for example, via indirect prompt injection against an agent running kubeshark mcp --allow-destructive—can use the pod regex variable to redirect the privileged worker, Hub, and front images to a malicious registry by overriding tap.docker.registry and tap.docker.tag. Since the deployed worker DaemonSet runs with privileged host networking and filesystem access, a malicious image can lead to full node and cluster-admin compromise.Recommendations
Update Kubeshark to version 53.4.0.
Do not run
kubeshark mcp with the --allow-destructive flag unless absolutely necessary.
Avoid exposing the MCP server to untrusted content or untrusted agent inputs.
Restrict the permissions of the kubeconfig used by the machine running the MCP server.Exploitability
Exploit
Fix
Impacts
Vendors
Affected products
Found an issue in the description? Have something to add? Feel free to write us 👾