How severe is GHSA-jpcj-7wfg-mqxv?

No CVSS score has been assigned to GHSA-jpcj-7wfg-mqxv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jpcj-7wfg-mqxv?

GHSA-jpcj-7wfg-mqxv affects the following packages: stata-mcp (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-jpcj-7wfg-mqxv?

Update stata-mcp to 1.13.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jpcj-7wfg-mqxv is resolved across your whole dependency graph.

How do I detect GHSA-jpcj-7wfg-mqxv in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for stata-mcp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-jpcj-7wfg-mqxv if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-jpcj-7wfg-mqxv?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-jpcj-7wfg-mqxv can be triaged on real exposure rather than presence alone.

Is GHSA-jpcj-7wfg-mqxv actively exploited in the wild?

No public exploit code has been indexed for GHSA-jpcj-7wfg-mqxv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-jpcj-7wfg-mqxv?

GHSA-jpcj-7wfg-mqxv has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 63th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-jpcj-7wfg-mqxv published, and has it been updated?

GHSA-jpcj-7wfg-mqxv was published on April 8, 2026 and was last updated on July 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

GHSA-jpcj-7wfg-mqxv — stata-mcp

Fix: SepineTam/stata-mcp#21

GHSA-jpcj-7wfg-mqxv is a security vulnerability in stata-mcp. A fix is available for stata-mcp — see the affected versions and patch details below.

stata-mcp has insufficient validation of user-supplied Stata do-file content that can lead to command execution

Also known asCVE-2026-31040PYSEC-2026-3076

Published

Apr 8, 2026

Updated

Jul 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 24, 2026 · OSV.dev, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs63th percentile — riskier than 63% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐍stata-mcp

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`stata-mcp`	all versions	1.13.0`pip install --upgrade 'stata-mcp==1.13.0'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for stata-mcp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update stata-mcp to 1.13.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jpcj-7wfg-mqxv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-jpcj-7wfg-mqxv can be triaged on real exposure rather than presence alone.

Tailored to GHSA-jpcj-7wfg-mqxv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-jpcj-7wfg-mqxv in your dependencies?

O3 Security finds GHSA-jpcj-7wfg-mqxv across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works