How severe is GHSA-v2gw-x5jf-pgwv?

No CVSS score has been assigned to GHSA-v2gw-x5jf-pgwv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v2gw-x5jf-pgwv?

GHSA-v2gw-x5jf-pgwv affects the following packages: mercurial (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-v2gw-x5jf-pgwv?

Update mercurial to 1.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v2gw-x5jf-pgwv is resolved across your whole dependency graph.

How do I detect GHSA-v2gw-x5jf-pgwv in my PyPI dependencies?

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

How do I mitigate GHSA-v2gw-x5jf-pgwv 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-v2gw-x5jf-pgwv?

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

Is GHSA-v2gw-x5jf-pgwv actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-v2gw-x5jf-pgwv, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-v2gw-x5jf-pgwv?

GHSA-v2gw-x5jf-pgwv has an EPSS (Exploit Prediction Scoring System) score of 1.9%, placing it in the 79th 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.

What type of vulnerability is GHSA-v2gw-x5jf-pgwv?

GHSA-v2gw-x5jf-pgwv is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-v2gw-x5jf-pgwv published, and has it been updated?

GHSA-v2gw-x5jf-pgwv was published on May 1, 2022 and was last updated on July 6, 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-v2gw-x5jf-pgwv — mercurial

GHSA-v2gw-x5jf-pgwv is a Path Traversal vulnerability in mercurial. 1 public exploit reference exists, so weaponization risk is real. A fix is available for mercurial — see the affected versions and patch details below.

Mercurial Directory traversal vulnerability

Also known asCVE-2008-2942PYSEC-2026-666

Published

May 1, 2022

Updated

Jul 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs79th percentile — riskier than 79% 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

🐍mercurial

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

Directory traversal vulnerability in patch.py in Mercurial before 1.0.2 allows user-assisted attackers to modify arbitrary files via ".." (dot dot) sequences in a patch file.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`mercurial`	all versions	1.0.2`pip install --upgrade 'mercurial==1.0.2'`

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Directory traversal vulnerability in patch.py in Mercurial 1.0.1 allows …

selenic.comNVDOct 2018

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mercurial, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mercurial to 1.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v2gw-x5jf-pgwv 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-v2gw-x5jf-pgwv can be triaged on real exposure rather than presence alone.

Tailored to GHSA-v2gw-x5jf-pgwv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Directory traversal vulnerability in patch.py in Mercurial before 1.0.2 allows user-assisted attackers to modify arbitrary files via ".." (dot dot) sequences in a patch file.

O3 Security · Impact-Aware SCA

Is GHSA-v2gw-x5jf-pgwv in your dependencies?

O3 Security finds GHSA-v2gw-x5jf-pgwv 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