MCP-for-Stata: Stata Command Injection via Unsanitized package in ado_package_install

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.4 · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2026-55071: 0.25% estimated exploitation activity in the next 30 days; percentile 16.75 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Stata Command Injection via Unsanitized package in adopackageinstall Summary The adopackageinstall MCP tool in stata-mcp concatenates user-controlled input directly into a Stata command string without any validation or sanitization. An attacker who can invoke the MCP tool or the equivalent Python API can embed newline characters in the package argument to inject arbitrary Stata commands. Because Stata supports a shell escape command, this leads to full OS-level arbitrary command execution (RCE) under the account running the Stata-MCP server. The tool is registered in the default all profile, so no non-default configuration is required. Base CVSS score is 8.4 (High). Details The vulnerability originates in SSCInstall.install(): The package parameter is interpolated into an f-string with no allowlist check, newline rejection, or quoting. The resulting command string is forwarded to the Stata interpreter verbatim: pexpect.sendline() writes the full multi-line string to the Stata REPL,…

Published by the source

12 Aug 2026, 19:23 UTC

Last modified by the source

12 Aug 2026, 19:23 UTC

Source last checked

26 Oct 2026, 13:50 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-49m4-vp58-wgc9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-55071

Advisory: MCP-for-Stata: Stata Command Injection via Unsanitized `package` in `ado_package_install`
IDs: CVE-2026-55071, GHSA-49m4-vp58-wgc9
Record: https://patchnext.com/advisories/cve-2026-55071 (revision 1, source checked 26 Oct 2026, 13:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: stata-mcp 1.19.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI stata-mcp: affected < 1.19.0; fixed in 1.19.0

## Suggested inspection (read-only)
- `python -m pip show stata-mcp`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on stata-mcp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-49m4-vp58-wgc9 (GitHub-reviewed advisory GHSA-49m4-vp58-wgc9 lists affected ranges: PyPI stata-mcp >=0 <1.19.0)

Commands are suggestions: review each one before running it.