CVE-2014-9390

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 76% (99th percentile of EPSS-scored CVEs). 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.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 76%
  • Public exploit code is available (Metasploit, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 76%CVSS: 9.8Exploit: Metasploit · epss top5pct · epss high · public exploitExposed services: Not assessed

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.8CRITICALmedium confidence
EG Risk
79
EG Risk 79/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation76% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
76%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

February 12, 2020

Last Modified

November 21, 2024

Advisory Details (5)

Auto-updated Oct 7, 2026
Patch available. Sources: github_commit.
generic

Git client vulnerability announced | Hacker News

https://news.ycombinator.com/item?id=8769667
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

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
generic
http://securitytracker.com/id?1031404

Patch Availability(1)

Vendor / EcosystemFix (by version range) / 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

(23 across 7 ecosystems)
Debian:11(5)
PackageVulnerable rangeFix by version rangeDependents
dulwich—
  • every version up to 0.10.1-1: fixed in 0.10.1-1
—
git—
  • every version up to 1:2.1.4-1: fixed in 1:2.1.4-1
—
jgit—
  • every version up to 3.7.0-1: fixed in 3.7.0-1
—
libgit2—
  • every version up to 0.21.3-1: fixed in 0.21.3-1
—
mercurial—
  • every version up to 3.1.2-2: fixed in 3.1.2-2
—
Debian:12(5)
PackageVulnerable rangeFix by version rangeDependents
dulwich—
  • every version up to 0.10.1-1: fixed in 0.10.1-1
—
git—
  • every version up to 1:2.1.4-1: fixed in 1:2.1.4-1
—
jgit—
  • every version up to 3.7.0-1: fixed in 3.7.0-1
—
libgit2—
  • every version up to 0.21.3-1: fixed in 0.21.3-1
—
mercurial—
  • every version up to 3.1.2-2: fixed in 3.1.2-2
—
Debian:13(5)
PackageVulnerable rangeFix by version rangeDependents
dulwich—
  • every version up to 0.10.1-1: fixed in 0.10.1-1
—
git—
  • every version up to 1:2.1.4-1: fixed in 1:2.1.4-1
—
jgit—
  • every version up to 3.7.0-1: fixed in 3.7.0-1
—
libgit2—
  • every version up to 0.21.3-1: fixed in 0.21.3-1
—
mercurial—
  • every version up to 3.1.2-2: fixed in 3.1.2-2
—
Debian:14(5)
PackageVulnerable rangeFix by version rangeDependents
dulwich—
  • every version up to 0.10.1-1: fixed in 0.10.1-1
—
git—
  • every version up to 1:2.1.4-1: fixed in 1:2.1.4-1
—
jgit—
  • every version up to 3.7.0-1: fixed in 3.7.0-1
—
libgit2—
  • every version up to 0.21.3-1: fixed in 0.21.3-1
—
mercurial—
  • every version up to 3.1.2-2: fixed in 3.1.2-2
—
Debian:6.0(1)
PackageVulnerable rangeFix by version rangeDependents
mercurial1.6.4-1
  • every version up to 1.6.4-1+deb6u1: fixed in 1.6.4-1+deb6u1
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.eclipse.jgit:org.eclipse.jgit1.2.0.201112221803-r ... 3.5.2.201411120430-r (23 versions)
  • every version up to 3.5.3: fixed in 3.5.3
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
mercurial0.8.1 ... 3.2.2 (78 versions)
  • every version up to 3.2.3: fixed in 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 / 15× 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-10-09 20:01 UTCEPSS rescore
  2. 2026-10-07 23:40 UTCEPSS rescore
  3. 2026-10-06 15:11 UTCEPSS rescore
  4. 2026-10-04 23:17 UTCEPSS rescore
  5. 2026-09-30 14:58 UTCEPSS rescore
  6. 2026-09-30 08:59 UTCEG score recompute
  7. 2026-09-28 13:45 UTCEPSS rescore
  8. 2026-09-27 09:32 UTCOSV refresh
  9. 2026-09-26 15:53 UTCEPSS rescore
  10. 2026-09-20 20:08 UTCEPSS rescore
  11. 2026-09-18 19:22 UTCEPSS rescore
  12. 2026-09-17 19:21 UTCEPSS rescore
  13. 2026-09-15 03:05 UTCEPSS rescore
  14. 2026-09-11 09:31 UTCEPSS rescore
  15. 2026-09-10 09:26 UTCEPSS rescore
  16. 2026-09-07 18:51 UTCOSV refresh
  17. 2026-09-06 13:42 UTCEPSS rescore
  18. 2026-09-05 15:23 UTCEPSS rescore
  19. 2026-09-04 13:55 UTCEPSS rescore
  20. 2026-09-02 14:07 UTCEPSS rescore
  21. 2026-08-30 19:12 UTCEPSS rescore
  22. 2026-08-26 14:41 UTCEPSS rescore
  23. 2026-08-25 13:44 UTCEPSS rescore
  24. 2026-08-21 23:44 UTCEPSS rescore
  25. 2026-08-21 04:44 UTCOSV refresh
Show 75 more
  1. 2026-08-19 16:59 UTCEPSS rescore
  2. 2026-08-16 02:09 UTCEPSS rescore
  3. 2026-08-12 13:46 UTCEPSS rescore
  4. 2026-08-08 16:31 UTCEPSS rescore
  5. 2026-08-07 16:22 UTCEPSS rescore
  6. 2026-08-06 13:42 UTCEPSS rescore
  7. 2026-08-05 19:54 UTCOSV refresh
  8. 2026-08-04 15:04 UTCEPSS rescore
  9. 2026-07-30 16:23 UTCEPSS rescore
  10. 2026-07-30 01:26 UTCEPSS rescore
  11. 2026-07-28 15:31 UTCEPSS rescore
  12. 2026-07-26 14:50 UTCEPSS rescore
  13. 2026-07-24 14:13 UTCEPSS rescore
  14. 2026-07-23 14:14 UTCEPSS rescore
  15. 2026-07-23 01:15 UTCEG score recompute
  16. 2026-07-23 00:18 UTCEG score recompute
  17. 2026-07-22 21:56 UTCEG score recompute
  18. 2026-07-22 14:04 UTCEPSS rescore
  19. 2026-07-21 15:21 UTCEPSS rescore
  20. 2026-07-21 15:21 UTCEPSS rescore
  21. 2026-07-20 17:03 UTCEPSS rescore
  22. 2026-07-19 19:18 UTCOSV refresh
  23. 2026-07-18 10:00 UTCEPSS rescore
  24. 2026-07-15 16:54 UTCEPSS rescore
  25. 2026-07-15 16:54 UTCEPSS rescore
  26. 2026-07-13 22:26 UTCEPSS rescore
  27. 2026-07-12 05:42 UTCEPSS rescore
  28. 2026-07-11 08:23 UTCEPSS rescore
  29. 2026-07-09 19:05 UTCEPSS rescore
  30. 2026-07-08 15:10 UTCEPSS rescore
  31. 2026-07-05 02:26 UTCEPSS rescore
  32. 2026-07-02 15:21 UTCEPSS rescore
  33. 2026-07-02 10:17 UTCOSV refresh
  34. 2026-07-01 15:02 UTCEPSS rescore
  35. 2026-07-01 15:02 UTCEPSS rescore
  36. 2026-06-30 23:19 UTCEPSS rescore
  37. 2026-06-30 23:19 UTCEPSS rescore
  38. 2026-06-28 04:53 UTCEPSS rescore
  39. 2026-06-27 03:05 UTCEPSS rescore
  40. 2026-06-25 13:47 UTCEPSS rescore
  41. 2026-06-25 13:47 UTCEPSS rescore
  42. 2026-06-23 21:30 UTCEPSS rescore
  43. 2026-06-22 14:23 UTCEPSS rescore
  44. 2026-06-22 14:22 UTCEPSS rescore
  45. 2026-06-21 01:57 UTCEPSS rescore
  46. 2026-06-21 01:57 UTCEPSS rescore
  47. 2026-06-18 17:50 UTCEPSS rescore
  48. 2026-06-18 17:49 UTCEPSS rescore
  49. 2026-06-17 17:49 UTCEPSS rescore
  50. 2026-06-15 17:45 UTCEPSS rescore
  51. 2026-06-14 23:14 UTCEPSS rescore
  52. 2026-06-14 09:13 UTCOSV refresh
  53. 2026-06-12 23:09 UTCEPSS rescore
  54. 2026-06-11 13:57 UTCEPSS rescore
  55. 2026-06-10 22:15 UTCEPSS rescore
  56. 2026-06-08 14:14 UTCEPSS rescore
  57. 2026-06-07 15:22 UTCEPSS rescore
  58. 2026-06-06 13:45 UTCEPSS rescore
  59. 2026-06-05 22:44 UTCEPSS rescore
  60. 2026-06-05 06:08 UTCEPSS rescore
  61. 2026-06-05 06:08 UTCEPSS rescore
  62. 2026-06-04 13:10 UTCEPSS rescore
  63. 2026-06-04 13:09 UTCEPSS rescore
  64. 2026-06-01 13:49 UTCEPSS rescore
  65. 2026-06-01 13:49 UTCEPSS rescore
  66. 2026-05-31 00:14 UTCEPSS rescore
  67. 2026-05-29 13:41 UTCEPSS rescore
  68. 2026-05-28 13:42 UTCEPSS rescore
  69. 2026-05-28 13:42 UTCEPSS rescore
  70. 2026-05-27 07:51 UTCEG score recompute
  71. 2026-05-27 07:51 UTCVendor advisory
  72. 2026-05-26 07:16 UTCEPSS rescore
  73. 2026-05-26 07:16 UTCEPSS rescore
  74. 2026-05-23 15:10 UTCEPSS rescore
  75. 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 product + 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 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. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 76% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
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?
A fix for CVE-2014-9390 is available: update to the fixed version the vendor names in its advisory.

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.

Book a Demo →Browse All CVEs