GPU VulnDB

Database/Control plane, storage & DevOps

Kubeshark MCP: download_file writes Hub responses to any local path an AI agent chooses

CVSS 5.3CVE-2026-129235Control plane, storage & DevOpscurated

Impact

From 53.1.0 up to 53.4.0, the download_file tool in kubeshark mcp writes Kubeshark Hub API responses to any destination path the caller names. An attacker who can steer the AI agent driving the MCP, for example through prompt injection, can overwrite any file the local MCP user can write. The bytes are limited to Hub API responses, and code execution has not been shown. Separately, Hub deployments run without authentication by default, so captured cluster network traffic stays readable there even after this fix.

Who can reach it

Local to the machine running kubeshark mcp. The attacker has to influence the tool arguments through the AI agent driving it (user interaction needed). No authentication. Reading captured traffic needs network access to a Hub deployment with authentication off.

What to do

Upgrade the Kubeshark CLI to 53.4.0 or later and restart any running kubeshark mcp process. That release does not change the Hub's default of no authentication, so turn on Hub authentication or limit network access to the Hub to keep captured traffic from being read.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.