CVE-2026-25905
The Python code being run by 'runPython' or 'runPythonAsync' is not …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- research.jfrog.com/vulnerabilities/mcp-run-python-lack-of-isolation-mcp-takeover-jfsa-2026
- nvd.nist.gov/vuln/detail/CVE-2026-25905
- research.jfrog.com/vulnerabilities/mcp-run-python-lack-of-isolation-mcp-takeover-jfsa-2026
- github.com/advisories/GHSA-pfv4-wmph-5gc6
- nvd.nist.gov/vuln/detail/CVE-2026-25905
- cve.org/CVERecord?id=CVE-2026-25905
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.