CVE-2026-47708
Command injection in MCP-for-Stata via unsanitized log_file_name parameter
Is CVE-2026-47708 being exploited?
Not confirmed. CVE-2026-47708 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.53% probability of exploitation in the next 30 days.
How severe is CVE-2026-47708?
CVE-2026-47708 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-47708?
Yes. A fix has been recorded for CVE-2026-47708. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-47708 affect?
CVE-2026-47708 affects MCP-for-Stata < 1.17.3, MCP server for Stata, Integrations using stata_do API/CLI. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-47708?
Upgrade to MCP-for-Stata 1.17.3; restrict access to the service and audit logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Inject Stata or shell/python commands via log_file_name, enabling remote code execution, file deletion, or arbitrary command execution.
Immediate action required
- affected< 1.17.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.