CVE-2026-129236
Kubeshark: MCP `start_kubeshark` argument injection via `pod_regex` → image redirect → cluster takeover
No exploitation reported by the sources we read.
- Published2026-11-16
- Fixed in0.0.2-0.20260812200004-a76a1920dc75
- WeaknessCWE-88
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2026-11-1616:49CVE publishedCNA
Versions per branch
OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 0.0 | ≥ 0.0.2-0.20260206182249-0bbbb473ea3f, < 0.0.2-0.20260812200004-a76a1920dc75 | 0.0.2-0.20260812200004-a76a1920dc75 | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA1 product
As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- kubesharkAffected
- = >= 53.1.0, < 53.4.0no fix stated
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-16
Fix
- Update kubeshark/kubeshark to 0.0.2-0.20260812200004-a76a1920dc75
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Metasploit modules
- none listed Metasploit Framework
Sources
- CNACVSS 3.17.22026-11-16
- CNAweakness (CWE)CWE-882026-11-16
- NVDweakness (CWE)CWE-88read 2026-11-16
- OSVaffected packages—
- GitHub AdvisoriesadvisoryHIGH2026-11-16
Identifiers
- EUVD-2026-126528same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-8vf2-hxg5-crqhsame flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H
- Published
- 2026-11-16
- Last Modified
- 2026-11-16
- NVD status
- Received
- GitHub Advisory
- GHSA-8vf2-hxg5-crqh
Frequently asked questions
What is CVE-2026-129236?
Is CVE-2026-129236 actively exploited?
What is the CVSS score for CVE-2026-129236?
Running kubeshark/kubeshark? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-8vf2-hxg5-crqh
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served