CVE-2019-1387

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory published 2022-05-24. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 4.4%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, and v2.14.6. Recursive clones are currently affected by a vulnerability that is caused by too-lax validation of submodule names, allowing very targeted attacks via remote code execution in recursive clones.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
41
EG Risk 41/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
Severity88% × 45%
Exploitation4% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
4.4%
EPSS %ILE
91st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). 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

December 18, 2019

Last Modified

November 4, 2025

Advisory Details (8)

Auto-updated Aug 12, 2026
Patch available. Sources: redhat.
generic

[ANNOUNCE] Git v2.24.1 and others

https://lore.kernel.org/git/xmqqr21cqcn9.fsf%40gitster-ct.c.googlers.com/T/#u
generic

[SECURITY] Fedora 30 Update: git-2.21.1-1.fc30 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/N6UGTEOXWIYSM5KDZL74QD2GK6YQNQCP/
genericMentions a patch (unverified)

[SECURITY] [DLA 3844-1] git security update

https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
genericMentions a patch (unverified)

[SECURITY] [DLA 2059-1] git security update

https://lists.debian.org/debian-lts-announce/2020/01/msg00019.html
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 8.0 Update Services for SAP Solutions.

https://access.redhat.com/errata/RHSA-2020:0228
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2020:0124
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2020:0002
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2019:4356

Vendor Advisories for CVE-2019-1387(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntugitweb (1:2.7.4-0ubuntu1.7) @ xenial2026-05-23ubuntu
redhatgit-0:2.18.2-1.el8_02020-01-27redhat
redhatgit-0:1.8.3.1-21.el7_72020-01-16redhat
redhatrh-git218-git-0:2.18.2-1.el72020-01-02redhat
redhatgit-0:2.18.2-1.el8_12019-12-19redhat

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

(26 across 25 ecosystems)
Alpine:v3.11(2)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.14.0 up to 2.24.1-r0: fixed in 2.24.1-r0
—
libgit2—
  • every version up to 0.28.4-r0: fixed in 0.28.4-r0
—
Alpine:v3.10(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.14.0 up to 2.22.2-r0: fixed in 2.22.2-r0
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.14.0 up to 2.24.1-r0: fixed in 2.24.1-r0
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.14.0 up to 2.24.1-r0: fixed in 2.24.1-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.14.0 up to 2.24.1-r0: fixed in 2.24.1-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.14.0 up to 2.24.1-r0: fixed in 2.24.1-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.14.0 up to 2.24.1-r0: fixed in 2.24.1-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.14.0 up to 2.24.1-r0: fixed in 2.24.1-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.14.0 up to 2.24.1-r0: fixed in 2.24.1-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.14.0 up to 2.24.1-r0: fixed in 2.24.1-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.14.0 up to 2.24.1-r0: fixed in 2.24.1-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.14.0 up to 2.24.1-r0: fixed in 2.24.1-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.14.0 up to 2.24.1-r0: fixed in 2.24.1-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.14.0 up to 2.24.1-r0: fixed in 2.24.1-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.14.0 up to 2.24.1-r0: fixed in 2.24.1-r0
—
Alpine:v3.7(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.14.0 up to 2.15.4-r0: fixed in 2.15.4-r0
—
Alpine:v3.8(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.14.0 up to 2.18.2-r0: fixed in 2.18.2-r0
—
Alpine:v3.9(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.14.0 up to 2.20.2-r0: fixed in 2.20.2-r0
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
git1:2.20.1-2
  • every version up to 1:2.20.1-2+deb10u9: fixed in 1:2.20.1-2+deb10u9
  • every version up to 1:2.20.1-2+deb10u1: fixed in 1:2.20.1-2+deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
git1:2.30.2-1, 1:2.30.2-1+deb11u1, 1:2.30.2-1+deb11u2
  • every version up to 1:2.30.2-1+deb11u3: fixed in 1:2.30.2-1+deb11u3
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • every version up to 1:2.24.0-2: fixed in 1:2.24.0-2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • every version up to 1:2.24.0-2: fixed in 1:2.24.0-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • every version up to 1:2.24.0-2: fixed in 1:2.24.0-2
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
git1:2.1.4-2.1 ... 1:2.1.4-2.1+deb8u7 (8 versions)
  • every version up to 1:2.1.4-2.1+deb8u8: fixed in 1:2.1.4-2.1+deb8u8
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
git1:2.11.0-3, 1:2.11.0-3+deb9u1, 1:2.11.0-3+deb9u2, 1:2.11.0-3+deb9u3, 1:2.11.0-3+deb9u4
  • every version up to 1:2.11.0-3+deb9u5: fixed in 1:2.11.0-3+deb9u5
—

Additional Vendor Advisories

(5)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 4× in last 7d / 24× 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.

Showing the most recent 100 of 157 total refreshes for this CVE.

  1. 2026-10-05 17:39 UTCEPSS rescore
  2. 2026-10-03 14:22 UTCEPSS rescore
  3. 2026-09-30 14:59 UTCEPSS rescore
  4. 2026-09-30 10:10 UTCEG score recompute
  5. 2026-09-28 13:46 UTCEPSS rescore
  6. 2026-09-27 13:40 UTCEPSS rescore
  7. 2026-09-26 15:54 UTCEPSS rescore
  8. 2026-09-26 15:54 UTCEPSS rescore
  9. 2026-09-26 00:20 UTCEPSS rescore
  10. 2026-09-24 13:59 UTCEPSS rescore
  11. 2026-09-23 13:43 UTCEPSS rescore
  12. 2026-09-22 14:43 UTCEPSS rescore
  13. 2026-09-21 20:28 UTCEPSS rescore
  14. 2026-09-20 20:10 UTCEPSS rescore
  15. 2026-09-19 16:30 UTCOSV refresh
  16. 2026-09-18 19:22 UTCEPSS rescore
  17. 2026-09-17 19:22 UTCEPSS rescore
  18. 2026-09-16 14:04 UTCEPSS rescore
  19. 2026-09-15 03:05 UTCEPSS rescore
  20. 2026-09-12 14:56 UTCEPSS rescore
  21. 2026-09-11 14:48 UTCEPSS rescore
  22. 2026-09-11 09:32 UTCEPSS rescore
  23. 2026-09-07 15:57 UTCEPSS rescore
  24. 2026-09-06 13:44 UTCEPSS rescore
  25. 2026-09-05 15:24 UTCEPSS rescore
Show 75 more
  1. 2026-09-04 13:56 UTCEPSS rescore
  2. 2026-09-02 14:07 UTCEPSS rescore
  3. 2026-09-01 03:32 UTCEPSS rescore
  4. 2026-08-31 19:34 UTCOSV refresh
  5. 2026-08-30 19:13 UTCEPSS rescore
  6. 2026-08-30 01:18 UTCEPSS rescore
  7. 2026-08-28 21:36 UTCEPSS rescore
  8. 2026-08-27 14:21 UTCEPSS rescore
  9. 2026-08-26 14:42 UTCEPSS rescore
  10. 2026-08-25 13:45 UTCEPSS rescore
  11. 2026-08-24 14:11 UTCEPSS rescore
  12. 2026-08-21 23:45 UTCEPSS rescore
  13. 2026-08-20 22:51 UTCEPSS rescore
  14. 2026-08-19 17:00 UTCEPSS rescore
  15. 2026-08-18 13:44 UTCEPSS rescore
  16. 2026-08-17 13:43 UTCEPSS rescore
  17. 2026-08-16 14:52 UTCEPSS rescore
  18. 2026-08-16 02:10 UTCEPSS rescore
  19. 2026-08-15 01:26 UTCEPSS rescore
  20. 2026-08-14 22:54 UTCOSV refresh
  21. 2026-08-12 13:47 UTCEPSS rescore
  22. 2026-08-09 13:43 UTCEPSS rescore
  23. 2026-08-08 16:33 UTCEPSS rescore
  24. 2026-08-07 16:23 UTCEPSS rescore
  25. 2026-08-06 13:43 UTCEPSS rescore
  26. 2026-08-05 19:13 UTCEPSS rescore
  27. 2026-08-04 15:05 UTCEPSS rescore
  28. 2026-08-02 02:23 UTCEPSS rescore
  29. 2026-08-01 04:12 UTCEPSS rescore
  30. 2026-07-30 16:24 UTCEPSS rescore
  31. 2026-07-30 11:14 UTCOSV refresh
  32. 2026-07-30 01:27 UTCEPSS rescore
  33. 2026-07-28 15:32 UTCEPSS rescore
  34. 2026-07-25 14:14 UTCEPSS rescore
  35. 2026-07-24 14:14 UTCEPSS rescore
  36. 2026-07-24 14:14 UTCEPSS rescore
  37. 2026-07-23 14:15 UTCEPSS rescore
  38. 2026-07-23 01:39 UTCEG score recompute
  39. 2026-07-22 22:20 UTCEG score recompute
  40. 2026-07-22 14:05 UTCEPSS rescore
  41. 2026-07-21 15:22 UTCEPSS rescore
  42. 2026-07-21 15:22 UTCEPSS rescore
  43. 2026-07-20 17:04 UTCEPSS rescore
  44. 2026-07-20 17:04 UTCEPSS rescore
  45. 2026-07-19 14:28 UTCEPSS rescore
  46. 2026-07-19 14:28 UTCEPSS rescore
  47. 2026-07-19 02:26 UTCEPSS rescore
  48. 2026-07-19 02:26 UTCEPSS rescore
  49. 2026-07-18 10:01 UTCEPSS rescore
  50. 2026-07-16 16:59 UTCEPSS rescore
  51. 2026-07-16 16:59 UTCEPSS rescore
  52. 2026-07-15 16:55 UTCEPSS rescore
  53. 2026-07-15 16:55 UTCEPSS rescore
  54. 2026-07-13 22:27 UTCEPSS rescore
  55. 2026-07-13 06:10 UTCEPSS rescore
  56. 2026-07-13 06:10 UTCEPSS rescore
  57. 2026-07-12 20:37 UTCOSV refresh
  58. 2026-07-12 05:43 UTCEPSS rescore
  59. 2026-07-12 05:43 UTCEPSS rescore
  60. 2026-07-11 08:24 UTCEPSS rescore
  61. 2026-07-11 08:24 UTCEPSS rescore
  62. 2026-07-09 19:06 UTCEPSS rescore
  63. 2026-07-08 15:11 UTCEPSS rescore
  64. 2026-07-07 13:43 UTCEPSS rescore
  65. 2026-07-06 16:25 UTCEPSS rescore
  66. 2026-07-06 16:25 UTCEPSS rescore
  67. 2026-07-06 02:20 UTCEPSS rescore
  68. 2026-07-05 02:27 UTCEPSS rescore
  69. 2026-07-04 06:28 UTCEPSS rescore
  70. 2026-07-01 15:03 UTCEPSS rescore
  71. 2026-07-01 15:03 UTCEPSS rescore
  72. 2026-06-30 23:20 UTCEPSS rescore
  73. 2026-06-29 14:03 UTCEPSS rescore
  74. 2026-06-28 04:54 UTCEPSS rescore
  75. 2026-06-28 04:54 UTCEPSS rescore

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2019-1387?
CVE-2019-1387 is a high vulnerability published on December 18, 2019. An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, and v2.14.6. Recursive clones are currently affected by a vulnerability that is caused by too-lax validation of submodule names, allowing very targeted attacks via remote code…
When was CVE-2019-1387 disclosed?
CVE-2019-1387 was first published on December 18, 2019, with the most recent update on November 4, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-1387 actively exploited?
CVE-2019-1387 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.4% probability of exploitation in the next 30 days (91st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-1387?
CVE-2019-1387 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2019-1387?
A fix for CVE-2019-1387 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2019-1387 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-1387

Explore →

Is Your Infrastructure Affected by CVE-2019-1387?

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

Book a Demo →Browse All CVEs