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.
CVE-2026-129236
“—” beside the score: it is equal to the CVSS score beside it.
Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-11-16. A secondary CVSS source baseline 7.2; sources differ by 0.0.
Also known asEUVD-2026-126528 (ENISA EUVD) · GHSA-8vf2-hxg5-crqh (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.2
- EG Score
- 7.2HIGHhigh confidence
- EG Risk
- 32EG Risk 32/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity72% × 45%Impact severity (EG Severity): CVSS 7.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.2% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.2%
- EPSS %ILE
- 12th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.2): severity, escalated by confirmed exploitation. This CVE's 7.2 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-17). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 16, 2026
Last Modified
November 17, 2026
Advisory Details (4)
Auto-updated Nov 16, 2026MCP `start_kubeshark` argument injection allows redirecting deployed images to an attacker-controlled registry · Advisory · kubeshark/kubeshark · GitHub
https://github.com/kubeshark/kubeshark/security/advisories/GHSA-8vf2-hxg5-crqhv53.4.0
Patch available: kubeshark/kubeshark v53.4.0
https://github.com/kubeshark/kubeshark/releases/tag/v53.4.0mcp: confine download_file destination and harden start_kubeshark argument handling
Fix merged in kubeshark/kubeshark PR #1957 on 2026-08-12 — awaiting tagged release
https://github.com/kubeshark/kubeshark/pull/1957commit a76a1920dc75 (kubeshark/kubeshark)
Fix landed in kubeshark/kubeshark commit a76a1920dc75 — awaiting tagged release
https://github.com/kubeshark/kubeshark/commit/a76a1920dc7587be700a17f1592f58a9512ad214Vendor Advisories for CVE-2026-129236(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| go | github.com/kubeshark/kubeshark @ 0.0.2-0.20260812200004-a76a1920dc75 (fixes >= 0.0.2-0.20260206182249-0bbbb473ea3f, < 0.0.2-0.20260812200004-a76a1920dc75) | — | ghsa |
These rows come from GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| github.com/kubeshark/kubeshark | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.2% · 12th percentile
- 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-11-19 20:26 UTCOSV refresh
- 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-11-17 17:29 UTCEchelonGraph re-scored
- 2026-11-17 17:29 UTCGHSA enrichmentGHSA-8vf2-hxg5-crqh · GitHub severity HIGH · GitHub CVSS 7.2
- 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-11-17 16:28 UTCEchelonGraph re-scored
- 2026-11-17 16:28 UTCGHSA enrichmentGHSA-8vf2-hxg5-crqh · GitHub severity HIGH · GitHub CVSS 7.2
- 2026-11-17 11:12 UTCEchelonGraph re-scored
- 2026-11-17 11:12 UTCGHSA enrichmentGHSA-8vf2-hxg5-crqh · GitHub severity HIGH · GitHub CVSS 7.2
- 2026-11-16 18:02 UTCENISA EUVD ID recordedEUVD-2026-126528 · Source: ENISA EUVD
- 2026-11-16 17:29 UTCEchelonGraph re-scored
- 2026-11-16 16:55 UTCEchelonGraph re-scoredFirst assessed: 7.2 HIGH
- 2026-11-16 16:54 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-129236?
When was the CVE record for CVE-2026-129236 published?
Is CVE-2026-129236 actively exploited?
What is the CVSS score of CVE-2026-129236?
How do I remediate CVE-2026-129236?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-129236
Is Your Infrastructure Affected by CVE-2026-129236?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.