CVE-2020-5260

CRITICALNVD 9.39.3
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.3 under NVD CVSS v3. EPSS exploit probability: 10.0%, top 5% 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
Trending — 3 sources updated this weekElevated
9.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 10%CVSS: 9.3Exploit: NoneExposed: 0

A fix is available — apply it.

Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host controlled by an attacker. Git uses external "credential helper" programs to store and retrieve passwords or other credentials from secure storage provided by the operating system. Specially-crafted URLs that contain an encoded newline can inject unintended values into the credential helper protocol stream, causing the credential helper to retrieve the password for one server (e.g., good.example.com) for an HTTP request being made to another server (e.g., evil.example.com), resulting in credentials for the former being sent to the latter. There are no restrictions on the relationship between the two, meaning that an attacker can craft a URL that will present stored credentials for any host to a host of their choosing. The vulnerability can be triggered by feeding a malicious URL to git clone. However, the affected URLs look rather suspicious; the likely vector would be through systems which automatically clone URLs not visible to the user, such as Git submodules, or package systems built around Git. The problem has been patched in the versions published on April 14th, 2020, going back to v2.17.x. Anyone wishing to backport the change further can do so by applying commit 9a6bbee (the full release includes extra checks for git fsck, but that commit is sufficient to protect clients against the vulnerability). The patched versions are: 2.17.4, 2.18.3, 2.19.4, 2.20.3, 2.21.2, 2.22.3, 2.23.2, 2.24.2, 2.25.3, 2.26.1.

CVSS v3
9.3
EG Score
9.3(medium)
EG Risk
62(Track*)
EG Risk 62/100SSVC: Track*

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
Severity93% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
95.1%
KEV
Not listed

Published

April 14, 2020

Last Modified

November 21, 2024

Advisory Details (8)

Auto-updated Jul 17, 2026
Patch available. Sources: github_commit, github.
generic

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

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/74Q7WVJ6FKLIN62VS2JD2XCNWK5TNKOW/
generic Patch Available

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

https://lists.debian.org/debian-lts-announce/2020/04/msg00010.html
github Patch Available

malicious URLs may cause Git to present stored credentials to the wrong server · Advisory · git/git · GitHub

https://github.com/git/git/security/advisories/GHSA-qm7j-c969-7j4q
github_commit

commit 9a6bbee8006c (git/git)

Fix landed in git/git commit 9a6bbee8006c — awaiting tagged release

https://github.com/git/git/commit/9a6bbee8006c24b46a85d29e7b38cfa79e9ab21b
generic

oss-security - CVE-2020-11008: Git: Malicious URLs can still cause Git to send a stored credential to the wrong server

http://www.openwall.com/lists/oss-security/2020/04/20/1
generic

oss-security - Re: CVE-2020-5260: Git: malicious URLs may cause Git to present stored credentials to the wrong server

http://www.openwall.com/lists/oss-security/2020/04/15/6
generic

oss-security - CVE-2020-5260: Git: malicious URLs may cause Git to present stored credentials to the wrong server

http://www.openwall.com/lists/oss-security/2020/04/15/5

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntugitweb (1:2.7.4-0ubuntu1.8) @ xenial2026-05-27ubuntu
redhatgit-0:1.8.3.1-23.el7_72020-08-31redhat
redhatgit-0:1.8.3.1-22.el7_82020-04-21redhat
redhatgit-0:2.18.2-2.el8_12020-04-21redhat
redhatgit-0:2.18.2-2.el8_02020-04-21redhat
redhatrh-git218-git-0:2.18.2-3.el72020-04-21redhat

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.

Weakness Classification(2)

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

All Vendor Advisories

(6)

Data Freshness Timeline

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

Publicly available exploits

(2 references)

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

  • GitHub PoCsv3nbeast/CVE-2020-5260
    First seen Apr 16, 2020

    CVE-2020-5260演示记录

    Open source ↗
  • GitHub PoCbrompwnie/cve-2020-5260
    First seen Apr 15, 2020

    A HTTP PoC Endpoint for cve-2020-5260 which can be deployed to Heroku

    Open source ↗

Frequently asked(5)

What is CVE-2020-5260?
CVE-2020-5260 is a critical vulnerability published on April 14, 2020. Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host controlled by an attacker. Git uses external "credential helper" programs to store and retrieve passwords or other credentials from secure storage provided by the operating system.…
When was CVE-2020-5260 disclosed?
CVE-2020-5260 was first published in the National Vulnerability Database on April 14, 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-2020-5260 actively exploited?
CVE-2020-5260 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 95.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-5260?
CVE-2020-5260 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2020-5260?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-5260, 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

Explore the affected products and dependency analysis for CVE-2020-5260

Explore →

Is Your Infrastructure Affected by CVE-2020-5260?

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