Git-Scm vulnerabilities1 known to be exploited.
Git-Scm has 37 published vulnerabilities across 1 product in our catalogue. 1 of them is on the list of flaws known to be exploited, so criminals are using them now. The most affected product is Git, with 37. If you run Git-Scm software, patch the exploited flaws first.
The most recent Git-Scm flaw added to the known-exploited list is CVE-2025-48384, on 25 August 2025. We keep watching the known-exploited list.
Which Git-Scm products have the most vulnerabilities?
Git leads with 37 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.
Which Git-Scm 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.
- 8.0Git Link Following Vulnerability
Git contains a link following vulnerability that stems from Git’s inconsistent handling of carriage return characters in configuration files.
Which Git-Scm 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.
- 97%CVE-2018-17456Critical
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...
- 89%CVE-2021-21300High
Git is an open-source distributed revision control system.
- 78%CVE-2017-1000117High
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.
- 56%CVE-2022-23521Critical
Git is distributed revision control system.
- 52%CVE-2023-25652High
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...
- 48%CVE-2018-11235High
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.
- 44%CVE-2022-41903Critical
Git is distributed revision control system.
- 36%CVE-2017-14867High
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...
- 18%CVE-2016-2324Critical
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.
All Git-Scm products we track.
1 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
Running Git-Scm? 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.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- 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.
1 flaw being exploited affects software Acme tracks
Git contains a link following vulnerability that stems from Git’s inconsistent handling of carriage return characters in configuration files.
- Matched to
- Git on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
Our catalogue lists 37 published vulnerabilities across 1 product and 657 versions from Git-Scm. The most recent Git-Scm flaw added to the known-exploited list is CVE-2025-48384, on 25 August 2025.
1 Git-Scm vulnerability is on the list of flaws known to be exploited. The most recently added is CVE-2025-48384. The full list is on this page.
Git, with 37 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the Git-Scm products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.