How severe is CVE-2014-9462?

CVE-2014-9462 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2014-9462?

CVE-2014-9462 affects the following packages: mercurial (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2014-9462?

Update mercurial to 3.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-9462 is resolved across your whole dependency graph.

How do I detect CVE-2014-9462 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 CVE-2014-9462 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.

Is CVE-2014-9462 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2014-9462, 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 CVE-2014-9462?

CVE-2014-9462 has an EPSS (Exploit Prediction Scoring System) score of 4.2%, placing it in the 91th 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 CVE-2014-9462?

CVE-2014-9462 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-9462 published, and has it been updated?

CVE-2014-9462 was published on March 31, 2015 and was last updated on April 16, 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

CRITICAL severity

CVE-2014-9462 — mercurial

CRITICAL

CVE-2014-9462 is a critical-severity (CVSS 9.8) Improper Input Validation vulnerability in mercurial. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for mercurial — see the affected versions and patch details below.

Mercurial vulnerable to arbitrary command execution via a crafted repository name in a clone command

Also known asGHSA-3pmw-h7j4-rf54PYSEC-2015-14

Published

Mar 31, 2015

Updated

Apr 16, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

4.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

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

The _validaterepo function in sshpeer in Mercurial before 3.2.4 allows remote attackers to execute arbitrary commands via a crafted repository name in a clone command.

Affected Packages

1 total 1 fixed

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

Affected Products

2 products · 3 configurations

Application

mercurialmercurial

≤ 3.2.3

range

opensuseopensuse

2 versions

13.113.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.

The _validaterepo function in sshpeer in Mercurial before 3.2.4 allows r…

chargen.matasano.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 3.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-9462 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.

Frequently Asked Questions

The _validaterepo function in sshpeer in Mercurial before 3.2.4 allows remote attackers to execute arbitrary commands via a crafted repository name in a clone command.

O3 Security · Impact-Aware SCA

Is CVE-2014-9462 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-20Improper Input Validation

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

Mar 31, 2015

First exploit

Oct 30, 2018

Last updated

Apr 16, 2026

Identifiers

CVE-2014-9462

GHSA-3pmw-h7j4-rf54

PYSEC-2015-14

References

Advisorymercurial.selenic.com · WhatsNew Advisorydebian.org · dsa 3257 Advisorysecurity.gentoo.org · 201612 19 Advisorynvd.nist.gov · CVE 2014 9462 Weblists.opensuse.org · msg00085 Weboracle.com · bulletinjul2015 2511963 Webosvdb.org Webgithub.com · PYSEC 2015 14.yaml Evidencechargen.matasano.com · this new vulnerability mercurial command injection cve 2014 9462

Related vulnerabilities

This CVE is critical severity; 2 of 8 other CVEs affecting mercurial are rated as high or higher (top: critical).

CVE-2016-3105CVE-2014-9390CVE-2016-3069CVE-2016-3630CVE-2017-1000115CVE-2016-3068CVE-2018-17983CVE-2018-13347

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedApr 16, 2026

CVE-2014-9462 — mercurial

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2014-9462 in your dependencies?