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

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.

Published: 2020-04-14 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2020-5260 is rated High Risk (71.8/100): CVSS Critical severity, with high exploitation likelihood (EPSS 37.88%, 97th percentile). Core evidence: EPSS ranks this CVE among the most likely to be exploited in the near term. Mandatory action: High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2020-5260

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-22 37.30% 37.88% +0.58%
2 2026-05-14 37.88% 37.30% -0.58%
3 2026-05-01 37.88%

Full EPSS history (44 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-5260

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.3 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 5.8 [email protected]
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
3.9 3.6 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
10.0 2.9 [email protected]

Weakness enumeration for CVE-2020-5260

OS Trackers for CVE-2020-5260

vendor priority summary link
alpine high CVE-2020-5260: 1 source package rows (git); 30 state rows across 10 repos (3.10-main, 3.11-main, 3.12-main, 3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 10, open 20. https://security.alpinelinux.org/vuln/CVE-2020-5260
debian not yet assigned CVE-2020-5260 not yet assigned priority: Debian including 1 source packages (git), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2020-5260
gentoo low CVE-2020-5260: 1 GLSA(s) (202004-13), 1 atom(s) (dev-vcs/git); latest impact low. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2020-5260
redhat high https://access.redhat.com/security/cve/CVE-2020-5260
suse high CVE-2020-5260 severity important: SUSE including 171 source package names (emacs-git-1.8.3.1-22.el7_8, emacs-git-el-1.8.3.1-22.el7_8, …), 379 product×package rows across 53 product lines (HPE Helion OpenStack 8, Image SLES12-SP5-SAP-Azure-LI-BYOS-Production, … (53 product lines)): Fixed 379. https://www.suse.com/security/cve/CVE-2020-5260/
ubuntu medium CVE-2020-5260 medium priority: Ubuntu including 1 source packages (git), 5 status rows across 5 suites (bionic, eoan, trusty, upstream, xenial): released 3, DNE 1, needs-triage 1. https://ubuntu.com/security/CVE-2020-5260

Affected software / configurations for CVE-2020-5260

Vendor Product Version Raw CPE
git git < 2.17.4 cpe:2.3:a:git:git:*:*:*:*:*:*:*:*
git git >= 2.22.0, < 2.22.3 cpe:2.3:a:git:git:*:*:*:*:*:*:*:*
git-scm git >= 2.18.0, < 2.18.3 cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*
git-scm git >= 2.19.0, < 2.19.4 cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*
git-scm git >= 2.20.0, < 2.20.3 cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*
git-scm git >= 2.21.0, < 2.21.2 cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*
git-scm git >= 2.23.0, < 2.23.2 cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*
git-scm git >= 2.24.0, < 2.24.2 cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*
git-scm git >= 2.25.0, < 2.25.3 cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*
git-scm git >= 2.26.0, < 2.26.1 cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*
canonical ubuntu_linux 16.04 cpe:2.3:o:canonical:ubuntu_linux:16.04:*:*:*:lts:*:*:*
canonical ubuntu_linux 18.04 cpe:2.3:o:canonical:ubuntu_linux:18.04:*:*:*:lts:*:*:*
canonical ubuntu_linux 19.10 cpe:2.3:o:canonical:ubuntu_linux:19.10:*:*:*:*:*:*:*
debian debian_linux 8.0 cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*
debian debian_linux 9.0 cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
fedoraproject fedora 30 cpe:2.3:o:fedoraproject:fedora:30:*:*:*:*:*:*:*
fedoraproject fedora 31 cpe:2.3:o:fedoraproject:fedora:31:*:*:*:*:*:*:*
fedoraproject fedora 32 cpe:2.3:o:fedoraproject:fedora:32:*:*:*:*:*:*:*
opensuse leap 15.1 cpe:2.3:o:opensuse:leap:15.1:*:*:*:*:*:*:*

References for CVE-2020-5260

URL Tags
http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00027.html Third Party Advisory
http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00003.html Third Party Advisory
http://packetstormsecurity.com/files/157250/Git-Credential-Helper-Protocol-Newline-Injection.html Third Party Advisory VDB Entry
http://www.openwall.com/lists/oss-security/2020/04/15/5 Mailing List
http://www.openwall.com/lists/oss-security/2020/04/15/6 Mailing List Third Party Advisory
http://www.openwall.com/lists/oss-security/2020/04/20/1 Mailing List Third Party Advisory
https://github.com/git/git/commit/9a6bbee8006c24b46a85d29e7b38cfa79e9ab21b Patch Third Party Advisory
https://github.com/git/git/security/advisories/GHSA-qm7j-c969-7j4q Mitigation Patch Third Party Advisory
https://lists.debian.org/debian-lts-announce/2020/04/msg00010.html Mailing List Third Party Advisory
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/74Q7WVJ6FKLIN62VS2JD2XCNWK5TNKOW/
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/7TVS5UG6JD3MYIGSBKMIOS6AF7CR5IPI/
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/MOCTR2SEHCPSCOVUQJAGFPGKFMI2VE6V/
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PN3FUOXKX3AXTULYV53ACABER2W2FSOU/
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/XPCEOIFLLEF24L6GLVJVFZX4CREDEHDF/
https://lore.kernel.org/git/xmqqy2qy7xn8.fsf%40gitster.c.googlers.com/
https://security.gentoo.org/glsa/202004-13 Third Party Advisory
https://support.apple.com/kb/HT211141 Third Party Advisory
https://usn.ubuntu.com/4329-1/ Third Party Advisory
https://www.debian.org/security/2020/dsa-4657 Third Party Advisory
cvelogic Threat Intelligence