AI Stack Alert Medium CVE-2026-129235 For CISO, SOC / IR, AppSec, AI Eng AI-assisted
Kubeshark MCP download_file tool allows unconfined file writes (CVE-2026-129235)
Kubeshark versions 53.1.0 through 53.4.0 contain a flaw in the download_file tool in cmd/mcpRunner.go. The tool accepts caller-controlled path and dest values and writes Hub API response bytes to dest without confining the destination. The destination-write issue is fixed in version 53.4.0.
Why it matters
An attacker who influences an AI agent driving kubeshark mcp can write Hub-supplied bytes to any path writable by the local MCP user. Captured network traffic may also be readable from default auth-disabled Hub deployments.
Do this
- Upgrade Kubeshark to version 53.4.0 or later.
- Identify hosts running kubeshark mcp in versions 53.1.0 through 53.4.0 and prioritize them for upgrade.
- Review whether Kubeshark Hub deployments have authentication enabled and enable it, since the fix does not address Hub-side default authentication.
- Restrict the local user account running the MCP server to least-privilege file write permissions.
Exploit Clock
No signals yet
- No exploitation signals yet
Signals
- NoCISA KEV
- 5.3CVSS
- NoPublic PoC
- 27/100Priority
- 80%Confidence
Evidence
“the download_file tool in cmd/mcpRunner.go accepts caller-controlled path and dest values”
“The destination-write issue is fixed in version 53.4.0.”
“Hub-side default authentication remains outside this remediation, so captured traffic can remain readable in default auth-disabled Hub deployments”
Sources
Affected / related
Kubeshark, kubeshark, kubeshark mcp
Published 2026-11-16 17:17 UTC · updated 2026-11-16 18:35 UTC · AI-assisted summary, checked against quoted sources · How we score