Skip to content

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

Moderate severity GitHub Reviewed Published Feb 9, 2026 to the GitHub Advisory Database • Updated Feb 11, 2026

Package

pip mcp-run-python (pip)

Affected versions

<= 0.0.22

Patched versions

None

Description

Impact

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.

Patches

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).

Workarounds

There are no configuration-based workarounds provided by the package itself. 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.

Resources

References

Published by the National Vulnerability Database Feb 9, 2026
Published to the GitHub Advisory Database Feb 9, 2026
Reviewed Feb 11, 2026
Last updated Feb 11, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:L

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(8th percentile)

Weaknesses

Server-Side Request Forgery (SSRF)

The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. Learn more on MITRE.

CVE ID

CVE-2026-25904

GHSA ID

GHSA-6fgp-m6q4-j3q5

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.