How severe is CVE-2014-9390?

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

Which packages are affected by CVE-2014-9390?

CVE-2014-9390 affects the following packages: org.eclipse.jgit:org.eclipse.jgit (Maven), mercurial (PyPI). Ecosystems affected: Maven, PyPI.

How do I fix CVE-2014-9390?

Update org.eclipse.jgit:org.eclipse.jgit to 3.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-9390 is resolved across your whole dependency graph.

How do I detect CVE-2014-9390 in my Maven, PyPI dependencies?

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

How do I mitigate CVE-2014-9390 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-9390 actively exploited in the wild?

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

CVE-2014-9390 has an EPSS (Exploit Prediction Scoring System) score of 75.6%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2014-9390?

CVE-2014-9390 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.

Is there exploit tooling available for CVE-2014-9390?

A Metasploit module references CVE-2014-9390, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

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

CVE-2014-9390 was published on February 12, 2020 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.

☕

☕ Maven🐍 PyPI

Not in CISA KEV

CRITICAL severity

CVE-2014-9390 — org.eclipse.jgit

CRITICALFix: libgit2/libgit2@928429c

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

JGit Improper Input Validation vulnerability

Also known asGHSA-6vvc-c2m3-cjf3PYSEC-2020-217

Published

Feb 12, 2020

Updated

Apr 16, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

75.6%probability of exploitation in next 30 days

Very High Risk0.00%

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

2 pkgs affected

☕org.eclipse.jgit:org.eclipse.jgit🐍mercurial

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

Description

Git before 1.8.5.6, 1.9.x before 1.9.5, 2.0.x before 2.0.5, 2.1.x before 2.1.4, and 2.2.x before 2.2.1 on Windows and OS X; Mercurial before 3.2.3 on Windows and OS X; Apple Xcode before 6.2 beta 3; mine all versions before 08-12-2014; libgit2 all versions up to 0.21.2; Egit all versions before 08-12-2014; and JGit all versions before 08-12-2014 allow remote Git servers to execute arbitrary commands via a tree containing a crafted .git/config file with (1) an ignorable Unicode codepoint, (2) a git~1/config representation, or (3) mixed case that is improperly handled on a case-insensitive filesystem.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.eclipse.jgit:org.eclipse.jgit`	all versions	3.5.3`org.eclipse.jgit:org.eclipse.jgit:3.5.3`
🐍PyPI	`mercurial`	all versions	3.2.3`pip install --upgrade 'mercurial==3.2.3'`

Affected Products

6 products · 13 configurations

Application

xcodeapple

≤ 6.1.1

1 version

6.2

Application

egiteclipse

< 08-12-2014

range

Application

jgiteclipse

≥ 3.5.0 && < 3.5.3

range

Application

gitgit-scm

≥ 2.2.0 && < 2.2.1

range

Application

libgit2libgit2

< 0.21.3

range

Application

mercurialmercurial

< 3.2.3

range

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.

Git before 1.8.5.6, 1.9.x before 1.9.5, 2.0.x before 2.0.5, 2.1.x before…

github.comMetasploitAug 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jgit:org.eclipse.jgit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.eclipse.jgit:org.eclipse.jgit to 3.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-9390 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

O3 Security · Impact-Aware SCA

Is CVE-2014-9390 in your dependencies?

Find it across Maven, 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

Timeline

Disclosed

Feb 12, 2020

First exploit

Aug 9, 2021

Last updated

Apr 16, 2026

Identifiers

CVE-2014-9390

GHSA-6vvc-c2m3-cjf3

PYSEC-2020-217

References

Advisorygit-blame.blogspot.com · git 1856 195 205 214 and 221 and Advisorymercurial.selenic.com · WhatsNew Advisorysecuritytracker.com · id Advisorysupport.apple.com · HT204147 Advisorygithub.com · 1938 git client vulnerability announced Advisorygithub.com · 928429c5c96a701bcbcafacb2421a82602b36915 Advisorynews.ycombinator.com · item Advisorynvd.nist.gov · CVE 2014 9390 Webarticle.gmane.org Weblibgit2.org · security Webgithub.com · PYSEC 2020 217.yaml Weblibgit2.org · security Webprojects.eclipse.org · 3.5.3 Webweb.archive.org · id

Related vulnerabilities

Also affects org.eclipse.jgit

This CVE is critical severity — higher than any of the other 2 CVEs affecting org.eclipse.jgit (highest there: high).

CVE-2025-4949CVE-2023-4759

Also affects mercurial

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

CVE-2016-3105CVE-2014-9462CVE-2016-3069CVE-2016-3630CVE-2017-1000115CVE-2016-3068

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedApr 16, 2026

CVE-2014-9390 — org.eclipse.jgit

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-9390 in your dependencies?