Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

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

Noroxi assessment

Priority: Monitor (action score 33/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 9.9% (FIRST EPSS); higher than 95.5% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: git (Alpine:v3.10) 2.22.3-r0; git (Alpine:v3.11) 2.24.2-r0; git (Alpine:v3.12) 2.26.1-r0.
  • Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to git (Alpine:v3.10) 2.22.3-r0; git (Alpine:v3.11) 2.24.2-r0; git (Alpine:v3.12) 2.26.1-r0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.5 · v3.1—Proof of concept Fix available
Published
Apr 14, 2020
Updated
Jun 16, 2026
EPSS
9.9% · 95th percentile

Report tools

JSON

Action score

33

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
3 / 30 · 9.9%

CNA vs NVD score

NVD
7.5
CNA · GitHub_M
9.3
1.8 point gap

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2020-5260

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
gitgit
git-scmgit
canonicalubuntu linux
debiandebian linux
fedoraprojectfedora
opensuseleap

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • canonical ubuntu linux16.04
  • canonical ubuntu linux18.04
  • canonical ubuntu linux19.10
  • debian debian linux10.0
  • debian debian linux8.0
  • debian debian linux9.0
  • fedoraproject fedora30
  • fedoraproject fedora31
  • fedoraproject fedora32
  • git gitbefore 2.17.4
  • git git2.22.0 and later · before 2.22.3
  • git-scm git2.26.0 and later · before 2.26.1
  • git-scm git2.25.0 and later · before 2.25.3
  • git-scm git2.24.0 and later · before 2.24.2
  • git-scm git2.23.0 and later · before 2.23.2
  • git-scm git2.21.0 and later · before 2.21.2
  • git-scm git2.20.0 and later · before 2.20.3
  • git-scm git2.19.0 and later · before 2.19.4
  • git-scm git2.18.0 and later · before 2.18.3
  • opensuse leap15.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • git git

    • < 2.17.4, >= 2.18.0, < 2.18.3, >= 2.19.0, 2.19.4, >= 2.20.0, < 2.20.3, >= 2.21.0, < 2.21.2, >= 2.22.0, < 2.22.3, >= 2.23.0, < 2.23.2, >= 2.24.0, < 2.24.2, >= 2.25.0, < 2.25.3, >= 2.26.0, < 2.26.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.10gitfrom 2.22.0 · before 2.22.3-r02.22.3-r0
Alpine:v3.11gitfrom 2.22.0 · before 2.24.2-r02.24.2-r0
Alpine:v3.12gitfrom 2.22.0 · before 2.26.1-r02.26.1-r0
Alpine:v3.8gitfrom 2.22.0 · before 2.18.3-r02.18.3-r0
Alpine:v3.9gitfrom 2.22.0 · before 2.20.3-r02.20.3-r0
Debian:10gitbefore 1:2.20.1-2+deb10u21:2.20.1-2+deb10u2
Debian:12gitbefore 1:2.26.1-11:2.26.1-1
Debian:8gitbefore 1:2.1.4-2.1+deb8u91:2.1.4-2.1+deb8u9
Debian:9gitbefore 1:2.11.0-3+deb9u61:2.11.0-3+deb9u6
openSUSE:Leap 15.1gitbefore 2.26.1-lp151.4.9.12.26.1-lp151.4.9.1
openSUSE:Leap 15.1gitbefore 2.16.4-lp151.4.6.12.16.4-lp151.4.6.1
openSUSE:Tumbleweedgitbefore 2.33.0-1.32.33.0-1.3
Red Hat:enterprise_linux:7::clientemacs-gitbefore 0:1.8.3.1-22.el7_80:1.8.3.1-22.el7_8
Red Hat:enterprise_linux:7::clientemacs-git-elbefore 0:1.8.3.1-22.el7_80:1.8.3.1-22.el7_8
Red Hat:enterprise_linux:7::clientgitbefore 0:1.8.3.1-22.el7_80:1.8.3.1-22.el7_8
Red Hat:enterprise_linux:7::clientgit-allbefore 0:1.8.3.1-22.el7_80:1.8.3.1-22.el7_8
Red Hat:enterprise_linux:7::clientgit-bzrbefore 0:1.8.3.1-22.el7_80:1.8.3.1-22.el7_8
Red Hat:enterprise_linux:7::clientgit-cvsbefore 0:1.8.3.1-22.el7_80:1.8.3.1-22.el7_8
Red Hat:enterprise_linux:7::clientgit-daemonbefore 0:1.8.3.1-22.el7_80:1.8.3.1-22.el7_8
Red Hat:enterprise_linux:7::clientgit-debuginfobefore 0:1.8.3.1-22.el7_80:1.8.3.1-22.el7_8
Red Hat:enterprise_linux:7::clientgit-emailbefore 0:1.8.3.1-22.el7_80:1.8.3.1-22.el7_8
Red Hat:enterprise_linux:7::clientgit-gnome-keyringbefore 0:1.8.3.1-22.el7_80:1.8.3.1-22.el7_8
Red Hat:enterprise_linux:7::clientgit-guibefore 0:1.8.3.1-22.el7_80:1.8.3.1-22.el7_8
Red Hat:enterprise_linux:7::clientgit-hgbefore 0:1.8.3.1-22.el7_80:1.8.3.1-22.el7_8

+87

Same product

git: all records

Other highest-scoring records for the same primary product.

  • CVE-2024-32002Git's recursive clones on case-insensitive filesystems that support symlinks are susceptible to Remote Code Execution
    45Plan
  • CVE-2022-25648The package git before 1.11.0 are vulnerable to Command Injection via git argument injection.
    40Plan
  • CVE-2025-48385Git alllows arbitrary file writes via bundle-uri parameter injection
    34Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2009-2108Jun 18, 2009 · git-daemon in git 1.4.4.5 through 1.6.3 allows remote attackers to cause a denial of service (infinite loop and CPU consumption) via a reque
    22Monitor
  • ← EarlierCVE-2010-3906Dec 17, 2010 · Cross-site scripting (XSS) vulnerability in Gitweb 1.7.3.3 and earlier allows remote attackers to inject arbitrary web script or HTML via th
    19Monitor
  • Later →CVE-2024-50349Jan 14, 2025 · Git does not sanitize URLs when asking for credentials interactively
    8Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:git2.22.3-r0 · Alpine:v3.10Package registry (OSV)
debian:git1:2.26.1-1 · Debian:12Package registry (OSV)
opensuse:git2.16.4-lp151.4.6.1 · openSUSE:Leap 15.1Package registry (OSV)
red hat:rh-git218-git0:2.18.2-3.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-git218-git-all0:2.18.2-3.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-git218-git-core0:2.18.2-3.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-git218-git-core-doc0:2.18.2-3.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-git218-git-cvs0:2.18.2-3.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-git218-git-daemon0:2.18.2-3.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-git218-git-debuginfo0:2.18.2-3.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-git218-git-email0:2.18.2-3.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-git218-git-gui0:2.18.2-3.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-git218-git-instaweb0:2.18.2-3.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-git218-git-p40:2.18.2-3.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-git218-git-subtree0:2.18.2-3.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
suse:git2.16.4-3.20.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP1Package registry (OSV)
suse:pcre210.34-1.3.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:perl-CGI4.38-1.3.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×3

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:372020-04-15
Proof-of-concept repository on GitHubstars:02020-04-15
Proof-of-concept repository on GitHubstars:112020-04-16

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoCsame day
  3. TodayOct 26, 2026+2386 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records