PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-47708 SepineTam CVE debrief

MCP-for-Stata is vulnerable to arbitrary Stata command injection due to unsanitized user input in the `log_file_name` parameter of the `stata_do` API and CLI. This issue, patched in version 1.17.3, allows attackers to execute arbitrary Stata commands, including `shell`, `python`, and `erase`, by crafting malicious input containing quotes, newlines, or Stata command separators.

Vendor
SepineTam
Product
stata-mcp
CVSS
CRITICAL 9.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-21
Original CVE updated
2026-07-22
Advisory published
2026-07-21
Advisory updated
2026-07-22

Who should care

Users of MCP-for-Stata versions prior to 1.17.3 should apply the patch to prevent arbitrary command injection. This vulnerability is particularly concerning for environments where Stata is integrated into larger systems or used by multiple users.

Technical summary

The `log_file_name` parameter in MCP-for-Stata's `stata_do` API and CLI is directly interpolated into a Stata command string without proper sanitization. The security guard, `GuardValidator`, only scans do-file content and does not validate this parameter. An attacker can inject arbitrary Stata commands by crafting a malicious `log_file_name` containing quotes, newlines, or Stata command separators. The vulnerability is patched in version 1.17.3.

Defensive priority

High priority should be given to updating MCP-for-Stata to version 1.17.3 or later. In the meantime, validate and sanitize all user input for the `log_file_name` parameter. Monitor system logs for suspicious Stata command activity.

Recommended defensive actions

  • Update MCP-for-Stata to version 1.17.3 or later
  • Validate and sanitize all user input for the `log_file_name` parameter
  • Monitor system logs for suspicious Stata command activity
  • Implement additional security measures to restrict Stata command execution
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record was published on 2026-07-21T21:16:51.477Z and was last modified on 2026-07-22T16:17:25.990Z. The NVD entry is currently 9.3 CRITICAL. Official references include GitHub commits, issues, and security advisories related to the vulnerability and patch.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-47708 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-47708

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-47708 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-47708

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.