MCP-for-Stata is a MCP server for integrating Stata into agent loops with a safety-first design. Prior to version 1.19.0, the ado_package_install 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. This issue has been patched in version 1.19.0.
CVE-2026-55071
HIGHPre-NVD 8.48.4
EchelonGraph scoreLOW confidence
This high-severity CVE scores 8.4 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: cna:github_m
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 8.4Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.4
- EG Score
- 8.4(low)
- EG Risk
- 38(Track*)EG Risk 38/100SSVC: Track*
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 computedSeverity84% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 12, 2026
Last Modified
September 21, 2026
Advisory Details (2)
Auto-updated Sep 21, 2026🔬 Proof of concept available. Patch available. Sources: github, github_release.
github_release Patch Available
V1.19.0
Patch available: SepineTam/mcp-for-stata v1.19.0
https://github.com/SepineTam/mcp-for-stata/releases/tag/v1.19.0github Patch Available🟡 PoC Available
Stata Command Injection via Unsanitized `package` in `ado_package_install` · Advisory · SepineTam/mcp-for-stata · GitHub
https://github.com/SepineTam/mcp-for-stata/security/advisories/GHSA-49m4-vp58-wgc9Vendor Advisories for CVE-2026-55071(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 (95 versions) | 1.19.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 1× in last 7d / 1× 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-09-21 15:00 UTCEG score recompute
- 2026-08-12 20:21 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-94
Frequently asked(4)
What is CVE-2026-55071?
CVE-2026-55071 is a high vulnerability published on August 12, 2026. MCP-for-Stata is a MCP server for integrating Stata into agent loops with a safety-first design. Prior to version 1.19.0, 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…
When was CVE-2026-55071 disclosed?
CVE-2026-55071 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on September 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-55071?
CVE-2026-55071 has a CVSS v4.0 base score of 8.4 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-55071?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55071, 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-55071
Is Your Infrastructure Affected by CVE-2026-55071?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.