VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

git: vulnerability history, versions and safety

git is a package in the RubyGems ecosystem. Vulert records 3 vulnerabilities for it across 32 releases, from Apr 2022 to Jan 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C1 H2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all git vulnerabilities

Vulert verdict on git 5.6.0 i

Updated on 23 Oct 2026

Good news: 5.6.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 76/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

What to do: Stay on 5.6.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 5.6.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 5.6.0 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 17 Jan 2023 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 1,799 i
  • OpenSSF scorecard 3/10 i
  • Last release 1 month ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by RubyGems, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for git, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
5.6.0 12 Sep 2026 none MIT — Details →
4.4.5 10 Sep 2026 none MIT — Details →
4.4.4 10 Sep 2026 none MIT — Details →
5.5.0 10 Sep 2026 none MIT — Details →
5.4.1 04 Sep 2026 none MIT — Details →
5.4.0 04 Sep 2026 none MIT — Details →
5.3.0 03 Sep 2026 none MIT — Details →
5.2.0 30 Aug 2026 none MIT — Details →
4.4.3 30 Aug 2026 none MIT — Details →
4.4.2 19 Aug 2026 none MIT — Details →
5.1.0 18 Aug 2026 none MIT — Details →
5.0.5 09 Aug 2026 none MIT — Details →
4.4.1 09 Aug 2026 none MIT — Details →
5.0.4 07 Aug 2026 none MIT — Details →
5.0.3 07 Aug 2026 none MIT — Details →
5.0.2 02 Aug 2026 none MIT — Details →
5.0.1 31 Jul 2026 none MIT — Details →
5.0.0 28 Jul 2026 none MIT — Details →
5.0.0.beta.5 14 Jul 2026 none MIT — Details →
5.0.0.beta.4 12 Jul 2026 none MIT — Details →
4.4.0 11 Jul 2026 none MIT — Details →
5.0.0.beta.3 26 Jun 2026 none MIT — Details →
5.0.0.beta.2 26 Jun 2026 none MIT — Details →
5.0.0.beta.1 04 Jun 2026 none MIT — Details →
4.3.2 31 Mar 2026 none MIT — Details →
4.3.1 20 Feb 2026 none MIT — Details →
4.3.0 15 Jan 2026 none MIT — Details →
4.2.0 11 Jan 2026 none MIT — Details →
4.1.2 10 Jan 2026 none MIT — Details →
4.1.1 09 Jan 2026 none MIT — Details →
4.1.0 02 Jan 2026 none MIT — Details →
4.0.7 29 Dec 2025 none MIT — Details →
4.0.6 11 Nov 2025 none MIT — Details →
4.0.5 20 Aug 2025 none MIT — Details →
4.0.4 09 Jul 2025 none MIT — Details →
4.0.2 08 Jul 2025 none MIT — Details →
4.0.1 07 Jul 2025 none MIT — Details →
4.0.0 02 Jul 2025 none MIT — Details →
3.1.1 02 Jul 2025 none MIT — Details →
3.1.0 18 May 2025 none MIT — Details →
3.0.2 15 May 2025 none MIT — Details →
3.0.1 14 May 2025 none MIT — Details →
3.0.0 27 Feb 2025 none MIT — Details →
2.3.3 04 Dec 2024 none MIT — Details →
2.3.2 19 Nov 2024 none MIT — Details →
2.3.1 23 Oct 2024 none MIT — Details →
2.3.0 01 Sep 2024 none MIT — Details →
2.2.0 26 Aug 2024 none MIT — Details →
2.1.1 01 Jun 2024 none MIT — Details →
2.1.0 31 May 2024 none MIT — Details →
2.0.1 21 May 2024 none MIT — Details →
2.0.0 11 May 2024 none MIT — Details →
2.0.0.pre3 15 Mar 2024 none MIT — Details →
2.0.0.pre2 24 Feb 2024 none MIT — Details →
2.0.0.pre1 15 Jan 2024 none MIT — Details →
1.19.1 13 Jan 2024 none MIT — Details →
1.19.0 29 Dec 2023 none MIT — Details →
1.18.0 19 Mar 2023 none MIT — Details →
1.17.2 07 Mar 2023 none MIT — Details →
1.17.1 06 Mar 2023 none MIT — Details →
1.17.0 06 Mar 2023 none MIT — Details →
1.16.0 04 Mar 2023 none MIT — Details →
1.15.0 01 Mar 2023 none MIT — Details →
1.14.0 26 Feb 2023 none MIT — Details →
1.13.2 02 Feb 2023 none MIT — Details →
1.13.1 12 Jan 2023 none MIT — Details →
1.13.0 14 Dec 2022 none MIT — Details →
1.12.0 18 Aug 2022 H2 MIT Yes Details →
1.11.0 17 Apr 2022 H2 MIT Yes Details →
1.10.2 06 Jan 2022 C1 H2 MIT Yes Details →
1.10.1 03 Jan 2022 C1 H2 MIT Yes Details →
1.10.0 20 Dec 2021 C1 H2 MIT Yes Details →
1.9.1 07 Jul 2021 C1 H2 MIT Yes Details →
1.9.0 06 Jul 2021 C1 H2 MIT Yes Details →
1.8.1 31 Dec 2020 C1 H2 MIT Yes Details →
1.8.0 31 Dec 2020 C1 H2 MIT Yes Details →
1.7.0 25 Apr 2020 C1 H2 MIT Yes Details →
1.6.0 02 Feb 2020 C1 H2 MIT Yes Details →
1.6.0.pre1 20 Jan 2020 C1 H2 MIT Yes Details →
1.5.0 10 Aug 2018 C1 H2 MIT Yes Details →
1.4.0 16 May 2018 C1 H2 MIT Yes Details →
1.3.0 25 Feb 2016 C1 H2 MIT Yes Details →
1.2.9.1 14 Jan 2015 C1 H2 MIT Yes Details →
1.2.9 12 Jan 2015 C1 H2 MIT Yes Details →
1.2.8 31 Jul 2014 C1 H2 MIT Yes Details →
1.2.7 09 Jun 2014 C1 H2 MIT Yes Details →
1.2.6 18 Aug 2013 C1 H2 MIT Yes Details →
1.2.5 17 Oct 2009 C1 H2 — Yes Details →
1.2.4 02 Oct 2009 C1 H2 — Yes Details →
1.2.3 01 Oct 2009 C1 H2 — Yes Details →
1.2.0 05 Aug 2009 C1 H2 — Yes Details →
1.2.2 02 Aug 2009 C1 H2 — Yes Details →
1.2.1 02 Aug 2009 C1 H2 — Yes Details →
1.0.1 25 Jul 2009 C1 H1 — Yes Details →
1.0.2 25 Jul 2009 C1 H1 — Yes Details →
1.0.3 25 Jul 2009 C1 H1 — Yes Details →
1.0.4 25 Jul 2009 C1 H1 — Yes Details →
1.0.5 25 Jul 2009 C1 H1 — Yes Details →
1.1.1 25 Jul 2009 C1 H1 — Yes Details →

All 99 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2023 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for git

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-25648: Command Injection in ruby-git 9.8 critical 1.11.0 20 Apr 2022
CVE-2022-46648: Remote Code Execution Vulnerability in ruby-git 8.0 high 1.13.0 09 Jan 2023
CVE-2022-47318: Code Injection in Ruby Git 8.0 high 1.13.0 17 Jan 2023

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About git

Is git safe to use?

Vulert records 3 vulnerabilities for git in RubyGems: 1 critical, 2 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is git's Vulert package health score?

Vulert scores git 76/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of git affected?

No. 5.6.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of git should I use?

5.6.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does git have?

3 vulnerabilities are recorded for git in the RubyGems ecosystem: 1 critical, 2 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new git vulnerabilities disclosed?

0 vulnerabilities were recorded for git in the last 12 months, and the oldest entry in this database dates to 20 Apr 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of git are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor git for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the git version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.