CVE-2014-9390

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 77.2%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Weaponized
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 63%
CISA-KEV: Not listedEPSS: 63%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
99.1%
KEV
Not listed

Published

February 12, 2020

Last Modified

November 21, 2024

Advisory Details (4)

Auto-updated Jul 6, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

Security (libgit2)

https://libgit2.org/security/
github_commit

commit 928429c5c96a (libgit2/libgit2)

Fix landed in libgit2/libgit2 commit 928429c5c96a — awaiting tagged release

https://github.com/libgit2/libgit2/commit/928429c5c96a701bcbcafacb2421a82602b36915
generic
http://securitytracker.com/id?1031404
generic

Git Blame: Git 1.8.5.6, 1.9.5, 2.0.5, 2.1.4 and 2.2.1 and thanking friends in Mercurial land

http://git-blame.blogspot.com/2014/12/git-1856-195-205-214-and-221-and.html

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntugit (1:2.1.0-1ubuntu0.1) @ utopic2026-05-27ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.eclipse.jgit:org.eclipse.jgit1.2.0.201112221803-r ... 3.5.2.201411120430-r (23 versions)3.5.3—
PyPI(1)
PackageVulnerable rangeFixed inDependents
mercurial0.8.1 ... 3.2.2 (78 versions)3.2.3—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 4× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:23 UTCEPSS rescore
  2. 2026-07-09 19:05 UTCEPSS rescore
  3. 2026-07-08 15:10 UTCEPSS rescore
  4. 2026-07-05 02:26 UTCEPSS rescore
  5. 2026-07-02 15:21 UTCEPSS rescore
  6. 2026-07-02 10:17 UTCOSV refresh
  7. 2026-07-01 15:02 UTCEPSS rescore
  8. 2026-07-01 15:02 UTCEPSS rescore
  9. 2026-06-30 23:19 UTCEPSS rescore
  10. 2026-06-30 23:19 UTCEPSS rescore
  11. 2026-06-28 04:53 UTCEPSS rescore
  12. 2026-06-27 03:05 UTCEPSS rescore
  13. 2026-06-25 13:47 UTCEPSS rescore
  14. 2026-06-25 13:47 UTCEPSS rescore
  15. 2026-06-23 21:30 UTCEPSS rescore
  16. 2026-06-22 14:23 UTCEPSS rescore
  17. 2026-06-22 14:22 UTCEPSS rescore
  18. 2026-06-21 01:57 UTCEPSS rescore
  19. 2026-06-21 01:57 UTCEPSS rescore
  20. 2026-06-18 17:50 UTCEPSS rescore
  21. 2026-06-18 17:49 UTCEPSS rescore
  22. 2026-06-17 17:49 UTCEPSS rescore
  23. 2026-06-15 17:45 UTCEPSS rescore
  24. 2026-06-14 23:14 UTCEPSS rescore
  25. 2026-06-14 09:13 UTCOSV refresh
Show 23 more
  1. 2026-06-12 23:09 UTCEPSS rescore
  2. 2026-06-11 13:57 UTCEPSS rescore
  3. 2026-06-10 22:15 UTCEPSS rescore
  4. 2026-06-08 14:14 UTCEPSS rescore
  5. 2026-06-07 15:22 UTCEPSS rescore
  6. 2026-06-06 13:45 UTCEPSS rescore
  7. 2026-06-05 22:44 UTCEPSS rescore
  8. 2026-06-05 06:08 UTCEPSS rescore
  9. 2026-06-05 06:08 UTCEPSS rescore
  10. 2026-06-04 13:10 UTCEPSS rescore
  11. 2026-06-04 13:09 UTCEPSS rescore
  12. 2026-06-01 13:49 UTCEPSS rescore
  13. 2026-06-01 13:49 UTCEPSS rescore
  14. 2026-05-31 00:14 UTCEPSS rescore
  15. 2026-05-29 13:41 UTCEPSS rescore
  16. 2026-05-28 13:42 UTCEPSS rescore
  17. 2026-05-28 13:42 UTCEPSS rescore
  18. 2026-05-27 07:51 UTCEG score recompute
  19. 2026-05-27 07:51 UTCVendor advisory
  20. 2026-05-26 07:16 UTCEPSS rescore
  21. 2026-05-26 07:16 UTCEPSS rescore
  22. 2026-05-23 15:10 UTCEPSS rescore
  23. 2026-05-23 07:01 UTCOSV refresh

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Metasploit module). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Metasploitexploit/multi/http/git_client_command_exec✓ verified
    First seen Dec 18, 2014

    Malicious Git and Mercurial HTTP Server For CVE-2014-9390

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2014-9390?
CVE-2014-9390 is a critical vulnerability published on February 12, 2020. 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…
When was CVE-2014-9390 disclosed?
CVE-2014-9390 was first published in the National Vulnerability Database on February 12, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2014-9390 actively exploited?
CVE-2014-9390 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2014-9390?
CVE-2014-9390 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2014-9390?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2014-9390, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2014-9390

Explore →

Is Your Infrastructure Affected by CVE-2014-9390?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs