stata-mcp has insufficient validation of user-supplied Stata do-file content that can lead to command execution
CVE-2026-31040 · GHSA-jpcj-7wfg-mqxv · published 2026-04-08
- Severity
- High
- CVSS score
- 8.7
- Chance of exploitation (EPSS)
- 0.57%
- Fixed in
- 1.13.0
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Total
- CISA SSVC
A vulnerability was identified in stata-mcp prior to v1.13.0 where insufficient validation of user-supplied Stata do-file content can lead to command execution.
Upgrade stata-mcp to 1.13.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| stata-mcp | PyPI | < 1.13.0 | 1.13.0 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.