Lack of isolation in mcp-run-python leads to MCP server takeover
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Mcp-run-python | Mcp-run-python |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-pfv4-wmph-5gc6 | MCP Run Python has a Sandbox Escape & Server Takeover Vulnerability |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.204% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mcp-run-python
Mcp-run-python mcp-run-python |
|
| Vendors & Products |
Mcp-run-python
Mcp-run-python mcp-run-python |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The Python code being run by 'runPython' or 'runPythonAsync' is not isolated from the rest of the JS code, allowing any Python code to use the Pyodide APIs to modify the JS environment. This may result in an attacker hijacking the MCP server - for malicious purposes including MCP tool shadowing. Note - the "mcp-run-python" project is archived and unlikely to receive a fix. | |
| Title | Lack of isolation in mcp-run-python leads to MCP server takeover | |
| Weaknesses | CWE-653 | |
| References |
| |
| Metrics |
cvssV3_1
|