MCP-for-Stata is an MCP server for Stata to integrate Stata into an agent. Prior to version 1.17.3, the log_file_name parameter in the stata_do 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 log_file_name containing quotes, newlines, or Stata command separators. Version 1.17.3 contains a patch for the issue.
CVE-2026-47708
CRITICALPre-NVD 9.39.3—Trending — 3 sources updated this weekElevated
EchelonGraph scoreMEDIUM confidence
This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.3Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.3
- EG Score
- 9.3(medium)
- EG Risk
- 73(Attend)EG Risk 73/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity93% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 22.4%
- KEV
- Not listed
Published
June 4, 2026
Last Modified
July 23, 2026
Advisory Details (3)
Auto-updated Jul 21, 2026🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available
Command injection via log_file_name parameter in Stata command wrapper · Advisory · SepineTam/mcp-for-stata · GitHub
https://github.com/SepineTam/mcp-for-stata/security/advisories/GHSA-4p62-hqp5-g644generic🟡 PoC Available
[Security] log_file_name parameter injection in Stata command wrapper · Issue #74 · SepineTam/mcp-for-stata · GitHub
https://github.com/SepineTam/mcp-for-stata/issues/74github_commit Patch Available
commit e6f945941ae0 (SepineTam/mcp-for-stata)
Patch available: SepineTam/mcp-for-stata v1.17.3 (contains commit e6f945941ae0)
https://github.com/SepineTam/mcp-for-stata/commit/e6f945941ae0c7cf5e74a428e0b3dc82b396382fVendor Advisories for CVE-2026-47708(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| stata-mcp | 0.1.0 ... 1.9.1 (91 versions) | 1.17.3 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:17 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 21:10 UTCEG score recompute▲ 9.30
- 2026-07-21 21:08 UTCMITRE cvelistV5CVSS v3 → 9.3 · CVSS v4 → 9.3
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-04 21:10 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-77
- CVE-2016-15057EG 9.9CRITICAL
- CVE-2014-5470EG 9.8EPSS 95%CRITICAL
- CVE-2013-2513EG 9.8CRITICAL
- CVE-2015-20108EG 9.8CRITICAL
- CVE-2015-10096NVD 5.0EG 9.8MEDIUM
- CVE-2017-20156NVD 5.5EG 9.8MEDIUM
- CVE-2016-20017EG 9.8 KEVEPSS 99%CRITICAL
- CVE-2016-4991EG 9.8CRITICAL
- CVE-2015-20107NVD 7.6EG 9.8EPSS 94%HIGH
- CVE-2014-4982EG 9.8EPSS 91%CRITICAL
Frequently asked(5)
What is CVE-2026-47708?
CVE-2026-47708 is a critical vulnerability published on June 4, 2026. MCP-for-Stata is an MCP server for Stata to integrate Stata into an agent. Prior to version 1.17.3, 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…
When was CVE-2026-47708 disclosed?
CVE-2026-47708 was first published in the National Vulnerability Database on June 4, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47708 actively exploited?
CVE-2026-47708 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47708?
CVE-2026-47708 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-47708?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47708, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47708
Is Your Infrastructure Affected by CVE-2026-47708?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.