UTC
Medium

MCP Run Python Deno Sandbox Misconfiguration Allows SSRF Attacks via Localhost Access

CVE-2026-25904 · GHSA-6fgp-m6q4-j3q5 · published 2026-02-09 · updated 2026-02-11

Severity
Medium
CVSS score
5.8
Chance of exploitation (EPSS)
0.19%
Fixed in
No fix yet
  • Exploitation Public proof of concept
  • Automatable No
  • Technical impact Partial
  • CISA SSVC
What it is

Server-Side Request Forgery (SSRF): A security vulnerability exists in the mcp-run-python tool (specifically within the Pydantic-AI integration) due to an overly permissive Deno sandbox configuration. The tool configures the Deno runtime—which is intended to isolate the execution of untrusted Python code—with network permissions that include access to the host's loopback interface (localhost). Consequently, malicious Python code executed through the tool can bypass network isolation and send HTTP requests to internal services running on the host machine. This allows attackers to interact with local APIs, databases, or cloud metadata services that should not be accessible from the sandbox.

What to do

No fixed release is listed yet for mcp-run-python. Follow the source advisory for updates, and until one ships:

From the advisory, shortened (GitHub Advisory Database, CC BY 4.0)
Remediation requires modifying the source code to restrict the Deno permissions (specifically removing or narrowing the --allow-net flag) or moving the execution to a container with no network access.

The full advisory →Licence

General guidance from ShieldPi, not a vendor fix

  • Server-side request forgery. Restrict its outbound network access to the hosts it needs, and keep internal addresses and cloud metadata endpoints out of its reach.

No Patch Available: The mcp-run-python project is currently archived and maintainers have indicated it is unlikely to receive a fix. Recommendation: Users are strongly advised to immediately stop using this package. If functionality is required, users must migrate to an alternative execution environment that enforces strict network isolation (e.g., blocking all outbound traffic or explicitly denying access to 127.0.0.1/::1).

Affected
PackageRegistryAffectedFixed in
mcp-run-pythonPyPI<= 0.0.22No fix yet

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].