Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.3amended

MCP-for-Stata: Command injection via log_file_name parameter in Stata command wrapper

CVE-2026-47708GHSA-4p62-hqp5-g644

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (stata-mcp 1.17.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
9.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-47708: 0.38% estimated exploitation activity in the next 30 days; percentile 32.54 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The logfilename parameter in the statado API and CLI is directly interpolated into a Stata command string without sanitization. The security guard (GuardValidator) only scans the do-file content but does not validate this parameter. An attacker can inject arbitrary Stata commands (including shell, python, erase, etc.) by crafting a malicious logfilename containing quotes, newlines, or Stata command separators. Details In src/statamcp/stata/statado/do.py, both executeunixlike and executewindows construct a Stata command string using Python f-strings: The generatelogcommand method returns: Where logfile is constructed from user-supplied logname: The logname parameter comes directly from user input (via MCP tool statado or CLI stata-mcp tool do) without any validation. Since the path is embedded inside double quotes in a Stata command string, an attacker can break out of the string context and inject arbitrary commands. Additionally, generatelogfile does not prevent path…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-4p62-hqp5-g644

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GHSA-4p62-hqp5-g644

  4. Revision 1 · created ·

    Published from ghsa record GHSA-4p62-hqp5-g644

Agent brief

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

# Patch Next advisory brief: CVE-2026-47708

Advisory: MCP-for-Stata: Command injection via log_file_name parameter in Stata command wrapper
IDs: CVE-2026-47708, GHSA-4p62-hqp5-g644
Record: https://patchnext.com/advisories/cve-2026-47708 (revision 4, source checked 26 Oct 2026, 13:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
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.17.3. A vendor fix does not mean a deployment is fixed.

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

## 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-4p62-hqp5-g644 (GitHub-reviewed advisory GHSA-4p62-hqp5-g644 lists affected ranges: PyPI stata-mcp >=0 <1.17.3)
- Verified: https://osv.dev/vulnerability/GHSA-4p62-hqp5-g644 (OSV record GHSA-4p62-hqp5-g644 lists affected ranges: PyPI stata-mcp >=0 <1.17.3 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…