CVE-2026-55071

HIGHPre-NVD 8.48.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (15th percentile of EPSS-scored CVEs). 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
Elevated
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.4Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.4
EG Score
8.4HIGHmedium confidence
EG Risk
54
EG Risk 54/100CISA SSVC

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 computed
Severity84% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
15th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 12, 2026

Last Modified

September 24, 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.0
github 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-wgc9

Vendor 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)
PackageVulnerable rangeFix by version rangeDependents
stata-mcp0.1.0 ... 1.9.1 (95 versions)
  • every version up to 1.19.0: fixed in 1.19.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 23× 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.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-03 19:56 UTCEG score recompute
  3. 2026-10-03 14:26 UTCEPSS rescore
  4. 2026-10-02 21:58 UTCEG score recompute
  5. 2026-10-02 17:56 UTCEPSS rescore
  6. 2026-10-02 08:19 UTCEG score recompute
  7. 2026-10-01 19:50 UTCEPSS rescore
  8. 2026-09-30 21:53 UTCEG score recompute
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-29 15:22 UTCEPSS rescore
  11. 2026-09-29 04:29 UTCEG score recompute
  12. 2026-09-28 13:51 UTCEPSS rescore
  13. 2026-09-28 01:17 UTCEG score recompute
  14. 2026-09-27 13:48 UTCEPSS rescore
  15. 2026-09-27 09:52 UTCEG score recompute
  16. 2026-09-26 15:59 UTCEPSS rescore
  17. 2026-09-24 21:25 UTCEG score recompute
  18. 2026-09-24 14:04 UTCEPSS rescore
  19. 2026-09-24 02:20 UTCEG score recompute
  20. 2026-09-23 17:54 UTCEPSS rescore
  21. 2026-09-22 14:59 UTCEG score recompute
  22. 2026-09-21 15:24 UTCEG score recompute
  23. 2026-09-21 15:00 UTCEG score recompute
  24. 2026-08-12 20:21 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

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 on August 12, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55071 actively exploited?
CVE-2026-55071 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55071?
CVE-2026-55071 has a CVSS base score of 8.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55071?
A fix for CVE-2026-55071 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55071 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55071

Explore →

Is Your Infrastructure Affected by CVE-2026-55071?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs