VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

git2: vulnerability history, versions and safety

git2 is a package in the crates.io ecosystem. Vulert records 5 vulnerabilities for it across 119 releases, from Jan 2023 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded L1 U4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 in the last 12 months

Most recent disclosure 13 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all git2 vulnerabilities

Vulert verdict on git2 0.21.0 i

Updated on 23 Oct 2026

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

Package health score 72/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 0.21.0 — unaffected i
  • Vulnerabilities on record 5 over 3 years · 4 in the last year i
  • Latest disclosure 13 May 2026 i
  • Highest CVSS 2.7 i
  • With no published fix 0 i
  • Depended on by 52 packages i
  • Stars 2,114 i
  • OpenSSF scorecard 4/10 i
  • Last release 5 months ago i
  • Licence Apache-2.0 OR MIT i

Version list, release dates, licence and dependants published by crates.io, refreshed 23 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 git2, 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
0.21.0 18 May 2026 none Apache-2.0 OR MIT — Details →
0.20.4 02 Feb 2026 U2 Apache-2.0 OR MIT Yes Details →
0.20.3 06 Dec 2025 L1 U3 Apache-2.0 OR MIT Yes Details →
0.20.2 05 May 2025 L1 U3 Apache-2.0 OR MIT Yes Details →
0.20.1 17 Mar 2025 L1 U3 Apache-2.0 OR MIT Yes Details →
0.20.0 05 Jan 2025 L1 U3 Apache-2.0 OR MIT Yes Details →
0.19.0 14 Jun 2024 L1 U3 Apache-2.0 OR MIT Yes Details →
0.18.3 19 Mar 2024 L1 U3 Apache-2.0 OR MIT Yes Details →
0.18.2 07 Feb 2024 L1 U3 Apache-2.0 OR MIT Yes Details →
0.18.1 20 Sep 2023 L1 U3 Apache-2.0 OR MIT Yes Details →
0.18.0 28 Aug 2023 L1 U3 Apache-2.0 OR MIT Yes Details →
0.17.2 28 May 2023 L1 U3 Apache-2.0 OR MIT Yes Details →
0.17.1 16 Apr 2023 L1 U3 Apache-2.0 OR MIT Yes Details →
0.17.0 02 Apr 2023 L1 U3 Apache-2.0 OR MIT Yes Details →
0.16.1 20 Jan 2023 L1 U3 Apache-2.0 OR MIT Yes Details →
0.16.0 10 Jan 2023 L1 U3 Apache-2.0 OR MIT Yes Details →
0.15.0 28 Jul 2022 L1 U4 Apache-2.0 OR MIT Yes Details →
0.14.4 10 May 2022 L1 U4 Apache-2.0 OR MIT Yes Details →
0.14.3 27 Apr 2022 L1 U4 Apache-2.0 OR MIT Yes Details →
0.14.2 10 Mar 2022 L1 U4 Apache-2.0 OR MIT Yes Details →
0.14.1 28 Feb 2022 L1 U4 Apache-2.0 OR MIT Yes Details →
0.14.0 24 Feb 2022 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.25 01 Dec 2021 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.24 16 Nov 2021 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.23 01 Oct 2021 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.22 08 Sep 2021 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.21 12 Aug 2021 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.20 24 May 2021 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.19 11 May 2021 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.18 19 Apr 2021 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.17 24 Jan 2021 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.16 21 Jan 2021 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.15 28 Dec 2020 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.14 22 Dec 2020 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.13 18 Dec 2020 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.12 14 Oct 2020 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.11 08 Sep 2020 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.10 21 Aug 2020 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.9 19 Aug 2020 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.8 21 Jul 2020 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.7 21 Jul 2020 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.6 19 May 2020 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.5 24 Apr 2020 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.4 23 Apr 2020 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.3 22 Apr 2020 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.2 10 Apr 2020 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.1 01 Apr 2020 L1 U4 Apache-2.0 OR MIT Yes Details →
0.13.0 13 Mar 2020 L1 U4 Apache-2.0 OR MIT Yes Details →
0.12.0 26 Feb 2020 L1 U4 Apache-2.0 OR MIT Yes Details →
0.11.0 12 Dec 2019 L1 U4 Apache-2.0 OR MIT Yes Details →
0.10.2 20 Nov 2019 L1 U4 Apache-2.0 OR MIT Yes Details →
0.10.1 09 Sep 2019 L1 U4 Apache-2.0 OR MIT Yes Details →
0.10.0 20 Aug 2019 L1 U4 Apache-2.0 OR MIT Yes Details →
0.9.2 24 Jul 2019 L1 U4 Apache-2.0 OR MIT Yes Details →
0.9.1 07 Jun 2019 L1 U4 Apache-2.0 OR MIT Yes Details →
0.9.0 04 Jun 2019 L1 U4 Apache-2.0 OR MIT Yes Details →
0.8.0 13 Dec 2018 L1 U4 Apache-2.0 OR MIT Yes Details →
0.7.5 02 Aug 2018 L1 U4 Apache-2.0 OR MIT Yes Details →
0.7.4 30 Jul 2018 L1 U4 Apache-2.0 OR MIT Yes Details →
0.7.3 22 Jul 2018 L1 U4 Apache-2.0 OR MIT Yes Details →
0.7.2 05 Jul 2018 L1 U4 Apache-2.0 OR MIT Yes Details →
0.7.1 22 Mar 2018 L1 U4 Apache-2.0 OR MIT Yes Details →
0.7.0 27 Feb 2018 L1 U4 Apache-2.0 OR MIT Yes Details →
0.6.11 08 Jan 2018 L1 U4 Apache-2.0 OR MIT Yes Details →
0.6.10 20 Dec 2017 L1 U4 Apache-2.0 OR MIT Yes Details →
0.6.9 10 Dec 2017 L1 U4 Apache-2.0 OR MIT Yes Details →
0.6.8 01 Sep 2017 L1 U4 Apache-2.0 OR MIT Yes Details →
0.6.7 29 Aug 2017 L1 U4 Apache-2.0 OR MIT Yes Details →
0.6.6 07 Jun 2017 L1 U4 Apache-2.0 OR MIT Yes Details →
0.6.5 09 May 2017 L1 U4 Apache-2.0 OR MIT Yes Details →
0.6.4 25 Jan 2017 L1 U4 Apache-2.0 OR MIT Yes Details →
0.6.3 28 Nov 2016 L1 U4 Apache-2.0 OR MIT Yes Details →
0.6.2 26 Nov 2016 L1 U4 Apache-2.0 OR MIT Yes Details →
0.6.1 24 Nov 2016 L1 U4 Apache-2.0 OR MIT Yes Details →
0.6.0 08 Nov 2016 L1 U4 Apache-2.0 OR MIT Yes Details →
0.5.2 08 Nov 2016 L1 U4 Apache-2.0 OR MIT Yes Details →
0.5.1 06 Nov 2016 L1 U4 Apache-2.0 OR MIT Yes Details →
0.5.0 05 Oct 2016 L1 U4 Apache-2.0 OR MIT Yes Details →
0.4.4 16 Jul 2016 L1 U4 Apache-2.0 OR MIT Yes Details →
0.4.3 28 Apr 2016 L1 U4 Apache-2.0 OR MIT Yes Details →
0.4.2 24 Feb 2016 L1 U4 Apache-2.0 OR MIT Yes Details →
0.4.1 24 Feb 2016 L1 U4 Apache-2.0 OR MIT Yes Details →
0.4.0 22 Feb 2016 L1 U4 Apache-2.0 OR MIT Yes Details →
0.3.5 22 Feb 2016 L1 U4 Apache-2.0 OR MIT Yes Details →
0.3.4 20 Jan 2016 L1 U4 Apache-2.0 OR MIT Yes Details →
0.3.3 19 Nov 2015 L1 U4 Apache-2.0 OR MIT Yes Details →
0.3.2 19 Oct 2015 L1 U4 Apache-2.0 OR MIT Yes Details →
0.3.1 03 Sep 2015 L1 U4 Apache-2.0 OR MIT Yes Details →
0.3.0 28 Jul 2015 L1 U4 Apache-2.0 OR MIT Yes Details →
0.2.14 27 Jul 2015 L1 U4 Apache-2.0 OR MIT Yes Details →
0.2.13 07 Jul 2015 L1 U4 Apache-2.0 OR MIT Yes Details →
0.2.12 11 Jun 2015 L1 U4 Apache-2.0 OR MIT Yes Details →
0.2.11 18 May 2015 L1 U4 Apache-2.0 OR MIT Yes Details →
0.2.10 13 May 2015 L1 U4 Apache-2.0 OR MIT Yes Details →
0.2.9 08 Apr 2015 L1 U4 Apache-2.0 OR MIT Yes Details →
0.2.8 03 Apr 2015 L1 U4 Apache-2.0 OR MIT Yes Details →
0.2.7 02 Apr 2015 L1 U4 Apache-2.0 OR MIT Yes Details →
0.2.6 25 Mar 2015 L1 U4 Apache-2.0 OR MIT Yes Details →
0.2.5 21 Mar 2015 L1 U4 Apache-2.0 OR MIT Yes Details →
0.2.4 19 Mar 2015 L1 U4 Apache-2.0 OR MIT Yes Details →
0.2.3 16 Mar 2015 L1 U4 — Yes Details →
0.2.2 15 Mar 2015 L1 U4 — Yes Details →
0.2.1 26 Feb 2015 L1 U4 — Yes Details →
0.2.0 25 Feb 2015 L1 U4 — Yes Details →
0.1.21 24 Feb 2015 L1 U4 — Yes Details →
0.1.20 20 Feb 2015 L1 U4 — Yes Details →
0.1.19 20 Feb 2015 L1 U4 — Yes Details →
0.1.18 15 Feb 2015 L1 U4 — Yes Details →
0.1.17 06 Feb 2015 L1 U4 — Yes Details →
0.1.16 06 Feb 2015 L1 U4 — Yes Details →
0.1.15 05 Feb 2015 L1 U4 — Yes Details →
0.1.13 28 Jan 2015 L1 U4 — Yes Details →
0.1.12 23 Jan 2015 L1 U4 — Yes Details →
0.1.11 18 Jan 2015 L1 U4 — Yes Details →
0.1.10 11 Jan 2015 L1 U4 — Yes Details →
0.1.9 08 Jan 2015 L1 U4 — Yes Details →
0.1.7 05 Jan 2015 L1 U4 — Yes Details →
0.1.6 03 Jan 2015 L1 U4 — Yes Details →
0.1.5 02 Jan 2015 L1 U4 — Yes Details →
0.1.4 31 Dec 2014 L1 U4 — Yes Details →

The newest 120 of 125 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for git2

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Undefined Behavior Risk in git2 Package Due to Buf Struct Dereferencing 2.7 low 0.20.4 04 Feb 2026
Insecure SSH Host Key Checking in git2 Rust Package N/A unrated 0.16.0 12 Jan 2023
Undefined Behavior Risk in git2 Package Due to Null Pointer Dereference N/A unrated 0.20.4 02 Feb 2026
Undefined Behavior in git2 Package: Remote::list() Null Pointer Issue N/A unrated 0.21.0 12 May 2026
Undefined Behavior in git2 Package: Null Pointer Dereference in BlameHunk Signatures N/A unrated 0.21.0 13 May 2026

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 git2

Is git2 safe to use?

Vulert records 5 vulnerabilities for git2 in crates.io: 0 critical, 0 high, 0 medium and 1 low, plus 4 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is git2's Vulert package health score?

Vulert scores git2 72/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 git2 affected?

No. 0.21.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 git2 should I use?

0.21.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 git2 have?

5 vulnerabilities are recorded for git2 in the crates.io ecosystem: 0 critical, 0 high, 0 medium and 1 low, plus 4 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new git2 vulnerabilities disclosed?

4 vulnerabilities were recorded for git2 in the last 12 months, and the oldest entry in this database dates to 12 Jan 2023. 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 git2 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 git2 for upcoming vulnerabilities?

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