CVE-2026-129236
7.2HighPublished 16 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite
High
0CVSS v3.110
- Attack vector
- Local
- Complexity
- High
- Privileges
- High
- User action
- Required
- Impact
- Full C/I/A compromise
- Weakness
- CWE-88
What an attacker gets
Attackers with high privileges can gain node and cluster-admin access by injecting malicious registry configurations. This requires the attacker to influence the pod_regex argument in the Kubeshark MCP tool.
Root cause
The tool fails to use an end-of-options separator when passing user-controlled input to the kubeshark tap command, allowing argument injection.
Affected versions
Kubeshark versions 53.1.0 through 53.3.x.
CVSS v3.1 · CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H
Fix & remediation
Upgrade to Kubeshark version 53.4.0 or later. Until you can upgrade, avoid using the --allow-destructive flag with the MCP tool.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD 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.