Quick answers
- Is CVE-2026-55071 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55071 being exploited in the wild.
- How severe is CVE-2026-55071?
- High severity, with a CVSS score of 8.4, published 21 September 2026.
- Which products and versions are affected?
- stata-mcp (PyPI) < 1.19.0, ECOSYSTEM:introduced=0,fixed=1.19.0.
- Is there a fix for CVE-2026-55071?
- Yes. stata-mcp (PyPI): upgrade to 1.19.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-55071 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-55071?
- Check whether you run stata-mcp (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- stata-mcp (PyPI): upgrade to 1.19.0 or later
pip install "stata-mcp>=1.19.0"
Technical details
The `ado_package_install` MCP tool in `stata-mcp` fails to sanitize the `package` argument before concatenating it into a Stata command string. Specifically, `SSC_Install.install()` interpolates user input into an f-string that is subsequently passed to the Stata REPL via `pexpect.sendline()`. An attacker can inject newline characters followed by Stata's `shell` or `!` commands to execute arbitrary OS-level commands. While a blacklist guard exists for dangerous commands, it is only applied to the `stata_do` path and does not protect the `ado-install` path. This vulnerability allows any principal capable of invoking the MCP tool—including AI agents or remote clients—to achieve Remote Code Execution (RCE) with the privileges of the Stata-MCP server process.
Affected products
- stata-mcp stata-mcp
Identifiers
- CVE-2026-55071
- GHSA-49m4-vp58-wgc9
- PYSEC-2026-3700
Timeline
- 2026-08-12: advisory: Advisory published on GitHub