← Back
CVE-2026-25905
Vulnerability in mcp-run-python (CVE-2026-25905)
Summary
vulnerability in mcp-run-python (CVE-2026-25905). Risk of unauthorized operations or information disclosure. Exploitable via ``runPython``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-25905** has been found in mcp-run-python.
Attackers can target a specific entry point like ``runPython`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "mcp-run-python CVE-2026-25905" on the vendor's site.
CVE-2026-25905 (mcp-run-python) — CWE-653 /
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `runPython` / `runPythonAsync`
Workaround: There are no configuration-based workarounds.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-653) exists in mcp-run-python. Attackers reach the vulnerable code path via ``runPython`` without authentication.
📍 Affected scope
mcp-run-python — . Attack surface: `runPython` / `runPythonAsync`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Workaround: There are no configuration-based workarounds.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'mcp-run-python' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mcp-run-python' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `mcp-run-python` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
There are no configuration-based workarounds.パッチが適用されるまでの応急処置として、There are no configuration-based workarounds. を実施。回避策の副作用 (機能低下) を確認した上で。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
mcp-run-python
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"0.0.22"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-25905
- advisory https://github.com/advisories/GHSA-pfv4-wmph-5gc6
- package https://github.com/pydantic/mcp-run-python
- package https://pypi.org/project/mcp-run-python
- web https://research.jfrog.com/vulnerabilities/mcp-run-python-lack-of-isolation-mcp-takeover-jfsa-2026-001653030