Secuno
ENNL
Book demo

CVE-2026-31040

Statamcp Stata-mcp code injection

9.8 CRITICALEPSS 1.06%
  1. Published8 Apr 2026

Description

A vulnerability was identified in stata-mcp prior to v1.13.0 where insufficient validation of user-supplied Stata do-file content can lead to command execution.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Statamcp Stata-mcp< 1.13.0

Remediation

Fixed in
Statamcp Stata-mcp≥ 1.13.0

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-891079.9
SAP S/4HANA (Manage Substitution/Validation Rules) does not sufficiently validate input…
CVE-2026-961199.9
IBM i 7.3, 7.4, 7.5, and 7.6 could allow a remote authenticated attacker to obtain…
CVE-2026-821088.8
IBM DataStage on Cloud Pak for Data 5.4.0.0 could allow a remote authenticated attacker…
CVE-2026-909209.8
IBM Maximo AI Service 9.1.0, and 9.2.0 could allow a remote attacker to execute…
CVE-2026-185378.7
IBM Maximo Application Suite - Location Service for Esri Component 9.2, 9.1, and 9.0 is…
CVE-2026-1093088.8
Craft CMS 4.0.0 before 4.18.7 and 5.0.0 before 5.10.14 passes the raw 'updates' request…

Frequently asked

Is CVE-2026-31040 being actively exploited?

CVE-2026-31040 is not in the CISA KEV catalog. Its EPSS exploit probability is 1.06%.

How severe is CVE-2026-31040?

CVE-2026-31040 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 1.06% probability of exploitation.

Which products are affected by CVE-2026-31040?

Affected products include Statamcp Stata-mcp.

How do I fix CVE-2026-31040?

Upgrade affected software to a fixed version, for example Statamcp Stata-mcp 1.13.0 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-31040 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.