Skip to content

CVE-2026-25905 Lack of isolation in mcp-run-python leads to MCP server takeover

MediumCVSS 5.8 EPSS 0.20%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
Proof of concept public · automatable: no · technical impact: partial

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.

Upgrade path

1 package: 1 fixed.

PackageAffectedFixed inStatus
pypi mcp-run-python(PyPI) <= 0.0.22; = 0; = 0.0.1; = 0.0.2 +3 more after 0.0.22 Fixed

Affected products

ProductAffected versionsFixed in
pypi mcp-run-python(PyPI) <= 0.0.22 No fix listed
pypi mcp-run-python(PyPI) = 0.0.1 No fix listed
pypi mcp-run-python(PyPI) = 0.0.2 No fix listed
pypi mcp-run-python(PyPI) = 0.0.20 No fix listed
pypi mcp-run-python(PyPI) = 0.0.21 No fix listed
pypi mcp-run-python(PyPI) = 0.0.22 No fix listed
pypi mcp-run-python(PyPI) = 0 No fix listed

References