Git vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited657 versions
The short answer

Git is made by Git-Scm. We track 37 published vulnerabilities in it, across 657 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 25 August 2025. If you run Git, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Git flaw added to the known-exploited list is CVE-2025-48384, on 25 August 2025. We keep watching the known-exploited list.

Versions

Which versions of Git do the exploited flaws hit?

Each exploited flaw lists the versions it affects, usually as ranges. "before 2.43.7" means every version up to, but not including, 2.43.7. Find your version, then patch.

  • CVE-2025-48384Exploited list, 25 Aug 2025

    Git Link Following Vulnerability

    before 2.43.72.44.0 to before 2.44.42.45.0 to before 2.45.42.46.0 to before 2.46.42.47.0 to before 2.47.32.48.0 to before 2.48.22.49.0 to before 2.49.12.50.0 to before 2.50.1
Known exploited

Which Git vulnerabilities are being exploited?

1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 8.0
    CVE-2025-48384HighKnown exploited
    Git Link Following Vulnerability

    Git contains a link following vulnerability that stems from Git’s inconsistent handling of carriage return characters in configuration files.

    Chance of use4.4%Known exploited since25 Aug 2025
Exploit likelihood

Which Git flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 97%

    Git before 2.14.5, 2.15.x before 2.15.3, 2.16.x before 2.16.5, 2.17.x before 2.17.2, 2.18.x before 2.18.1, and 2.19.x before 2.19.1 allows remote code execution during processing of a recursive "git clone" of a...

    CVSS9.8Published6 Oct 2018
  2. 89%

    Git is an open-source distributed revision control system.

    CVSS7.5Published9 Mar 2021
  3. 78%

    A malicious third-party can give a crafted "ssh://..." URL to an unsuspecting victim, and an attempt to visit the URL can result in any program that exists on the victim's machine being executed.

    CVSS8.8Published5 Oct 2017
  4. 56%

    Git is distributed revision control system.

    CVSS9.8Published17 Jan 2023
  5. 52%

    Git is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, by feeding specially crafted input to `git apply --reject`, a path...

    CVSS7.5Published25 Apr 2023
  6. 48%

    In Git before 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2.17.1, remote code execution can occur.

    CVSS7.8Published30 May 2018
  7. 44%

    Git is distributed revision control system.

    CVSS9.8Published17 Jan 2023
  8. 36%

    Git before 2.10.5, 2.11.x before 2.11.4, 2.12.x before 2.12.5, 2.13.x before 2.13.6, and 2.14.x before 2.14.2 uses unsafe Perl scripts to support subcommands such as cvsserver, which allows attackers to execute...

    CVSS8.8Published29 Sep 2017
  9. 18%

    Integer overflow in Git before 2.7.4 allows remote attackers to execute arbitrary code via a (1) long filename or (2) many nested trees, which triggers a heap-based buffer overflow.

    CVSS9.8Published8 Apr 2016
Precursor Intelligence

Running Git? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 37 published vulnerabilities listed under the name Git, across 657 versions. The most recent Git flaw added to the known-exploited list is CVE-2025-48384, on 25 August 2025.

1 is on the list of flaws known to be exploited. The most recently added is CVE-2025-48384.

Each flaw names its own versions, usually as ranges. The newest, CVE-2025-48384, affects before 2.43.7, 2.44.0 to before 2.44.4, 2.45.0 to before 2.45.4, 2.46.0 to before 2.46.4 and more. The versions for every exploited flaw are listed on this page.

Create a Precursor Intelligence account and track Git. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.