VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

libgit2-sys: vulnerability history, versions and safety

libgit2-sys is a package in the crates.io ecosystem. Vulert records 4 vulnerabilities for it across 109 releases, from Jan 2023 to Feb 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H1 M1 U2
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 libgit2-sys vulnerabilities

Vulert verdict on libgit2-sys 0.10.0 i

Updated on 23 Oct 2026

Action needed: 0.10.0 has 3 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 66/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Quiet

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 0.10.0 — affected i
  • Vulnerabilities on record 4 over 1 year · 0 in the last year i
  • Latest disclosure 12 Feb 2024 i
  • Highest CVSS 8.6 i
  • With no published fix 0 i
  • Depended on by 48 packages i
  • Stars 2,114 i
  • OpenSSF scorecard 4/10 i
  • Last release 82 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 libgit2-sys, 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.18.8+1.9.7 21 Aug 2026 none Apache-2.0 OR MIT — Details →
0.18.7+1.9.6 22 Jul 2026 none Apache-2.0 OR MIT — Details →
0.18.6+1.9.5 22 Jul 2026 none Apache-2.0 OR MIT — Details →
0.18.5+1.9.4 29 May 2026 none Apache-2.0 OR MIT — Details →
0.18.4+1.9.3 08 May 2026 none Apache-2.0 OR MIT — Details →
0.18.3+1.9.2 06 Dec 2025 none Apache-2.0 OR MIT — Details →
0.18.2+1.9.1 21 Jun 2025 none Apache-2.0 OR MIT — Details →
0.18.1+1.9.0 17 Mar 2025 none Apache-2.0 OR MIT — Details →
0.18.0+1.9.0 05 Jan 2025 none Apache-2.0 OR MIT — Details →
0.17.0+1.8.1 14 Jun 2024 none Apache-2.0 OR MIT — Details →
0.16.2+1.7.2 07 Feb 2024 none Apache-2.0 OR MIT — Details →
0.16.1+1.7.1 28 Aug 2023 H1 U1 Apache-2.0 OR MIT Yes Details →
0.16.0+1.7.1 28 Aug 2023 H1 U1 Apache-2.0 OR MIT Yes Details →
0.15.2+1.6.4 28 May 2023 H1 U1 Apache-2.0 OR MIT Yes Details →
0.15.1+1.6.4 16 Apr 2023 H1 U1 Apache-2.0 OR MIT Yes Details →
0.15.0+1.6.3 02 Apr 2023 H1 U1 Apache-2.0 OR MIT Yes Details →
0.14.2+1.5.1 20 Jan 2023 H1 U1 Apache-2.0 OR MIT Yes Details →
0.13.5+1.4.5 20 Jan 2023 H1 U1 Apache-2.0 OR MIT Yes Details →
0.14.1+1.5.0 10 Jan 2023 H1 M1 U1 Apache-2.0 OR MIT Yes Details →
0.14.0+1.5.0 28 Jul 2022 H1 M1 U1 Apache-2.0 OR MIT Yes Details →
0.13.4+1.4.2 10 May 2022 H1 U2 Apache-2.0 OR MIT Yes Details →
0.13.3+1.4.2 27 Apr 2022 H1 U2 Apache-2.0 OR MIT Yes Details →
0.13.2+1.4.2 10 Mar 2022 H1 U2 Apache-2.0 OR MIT Yes Details →
0.13.1+1.4.2 28 Feb 2022 H1 U2 Apache-2.0 OR MIT Yes Details →
0.13.0+1.4.1 24 Feb 2022 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.26+1.3.0 01 Dec 2021 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.25+1.3.0 16 Nov 2021 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.24+1.3.0 01 Oct 2021 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.23+1.2.0 08 Sep 2021 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.22+1.1.0 12 Aug 2021 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.21+1.1.0 24 May 2021 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.20+1.1.0 11 May 2021 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.19+1.1.0 19 Apr 2021 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.18+1.1.0 21 Jan 2021 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.17+1.1.0 28 Dec 2020 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.16+1.1.0 22 Dec 2020 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.15+1.1.0 18 Dec 2020 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.14+1.1.0 14 Oct 2020 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.13+1.0.1 08 Sep 2020 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.12+1.0.1 21 Aug 2020 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.11+1.0.1 19 Aug 2020 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.9+1.0.1 21 Jul 2020 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.8+1.0.1 21 Jul 2020 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.7+1.0.0 03 Jun 2020 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.6+1.0.0 19 May 2020 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.5+1.0.0 24 Apr 2020 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.4+1.0.0 22 Apr 2020 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.3+1.0.0 10 Apr 2020 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.2+1.0.0 01 Apr 2020 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.1+0.99.0 01 Apr 2020 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.0+0.99.0 13 Mar 2020 H1 U2 Apache-2.0 OR MIT Yes Details →
0.11.0+0.99.0 26 Feb 2020 H1 U2 Apache-2.0 OR MIT Yes Details →
0.10.0 12 Dec 2019 H1 U2 Apache-2.0 OR MIT Yes Details →
0.9.2 20 Nov 2019 H1 U2 Apache-2.0 OR MIT Yes Details →
0.9.1 09 Sep 2019 H1 U2 Apache-2.0 OR MIT Yes Details →
0.9.0 20 Aug 2019 H1 U2 Apache-2.0 OR MIT Yes Details →
0.8.2 24 Jul 2019 H1 U2 Apache-2.0 OR MIT Yes Details →
0.8.1 17 Jun 2019 H1 U2 Apache-2.0 OR MIT Yes Details →
0.8.0 04 Jun 2019 H1 U2 Apache-2.0 OR MIT Yes Details →
0.7.11 13 Dec 2018 H1 U2 Apache-2.0 OR MIT Yes Details →
0.7.10 25 Sep 2018 H1 U2 Apache-2.0 OR MIT Yes Details →
0.7.9 21 Sep 2018 H1 U2 Apache-2.0 OR MIT Yes Details →
0.7.8 13 Sep 2018 H1 U2 Apache-2.0 OR MIT Yes Details →
0.7.7 30 Jul 2018 H1 U2 Apache-2.0 OR MIT Yes Details →
0.7.6 22 Jul 2018 H1 U2 Apache-2.0 OR MIT Yes Details →
0.7.5 13 Jul 2018 H1 U2 Apache-2.0 OR MIT Yes Details →
0.7.4 05 Jul 2018 H1 U2 Apache-2.0 OR MIT Yes Details →
0.7.3 31 May 2018 H1 U2 Apache-2.0 OR MIT Yes Details →
0.7.2 29 May 2018 H1 U2 Apache-2.0 OR MIT Yes Details →
0.7.1 07 Mar 2018 H1 U2 Apache-2.0 OR MIT Yes Details →
0.7.0 27 Feb 2018 H1 U2 Apache-2.0 OR MIT Yes Details →
0.6.19 08 Jan 2018 H1 U2 Apache-2.0 OR MIT Yes Details →
0.6.18 20 Dec 2017 H1 U2 Apache-2.0 OR MIT Yes Details →
0.6.17 10 Dec 2017 H1 U2 Apache-2.0 OR MIT Yes Details →
0.6.16 04 Oct 2017 H1 U2 Apache-2.0 OR MIT Yes Details →
0.6.15 19 Sep 2017 H1 U2 Apache-2.0 OR MIT Yes Details →
0.6.14 29 Aug 2017 H1 U2 Apache-2.0 OR MIT Yes Details →
0.6.13 01 Aug 2017 H1 U2 Apache-2.0 OR MIT Yes Details →
0.6.12 07 Jun 2017 H1 U2 Apache-2.0 OR MIT Yes Details →
0.6.11 26 May 2017 H1 U2 Apache-2.0 OR MIT Yes Details →
0.6.10 09 May 2017 H1 U2 Apache-2.0 OR MIT Yes Details →
0.6.9 30 Apr 2017 H1 U2 Apache-2.0 OR MIT Yes Details →
0.6.8 24 Apr 2017 H1 U2 Apache-2.0 OR MIT Yes Details →
0.6.7 15 Feb 2017 H1 U2 Apache-2.0 OR MIT Yes Details →
0.6.6 05 Jan 2017 H1 U2 Apache-2.0 OR MIT Yes Details →
0.6.5 02 Dec 2016 H1 U2 Apache-2.0 OR MIT Yes Details →
0.6.4 26 Nov 2016 H1 U2 Apache-2.0 OR MIT Yes Details →
0.6.3 24 Nov 2016 H1 U2 Apache-2.0 OR MIT Yes Details →
0.6.2 11 Nov 2016 H1 U2 Apache-2.0 OR MIT Yes Details →
0.6.1 10 Nov 2016 H1 U2 Apache-2.0 OR MIT Yes Details →
0.4.6 08 Nov 2016 H1 U2 Apache-2.0 OR MIT Yes Details →
0.6.0 08 Nov 2016 H1 U2 Apache-2.0 OR MIT Yes Details →
0.5.3 08 Nov 2016 H1 U2 Apache-2.0 OR MIT Yes Details →
0.5.2 06 Nov 2016 H1 U2 Apache-2.0 OR MIT Yes Details →
0.5.1 17 Oct 2016 H1 U2 Apache-2.0 OR MIT Yes Details →
0.5.0 05 Oct 2016 H1 U2 Apache-2.0 OR MIT Yes Details →
0.4.5 07 Aug 2016 H1 U2 Apache-2.0 OR MIT Yes Details →
0.4.4 16 Jul 2016 H1 U2 Apache-2.0 OR MIT Yes Details →
0.4.3 28 Apr 2016 H1 U2 Apache-2.0 OR MIT Yes Details →
0.4.2 22 Mar 2016 H1 U2 Apache-2.0 OR MIT Yes Details →
0.3.12 09 Mar 2016 H1 U2 — Yes Details →
0.4.1 09 Mar 2016 H1 U2 — Yes Details →
0.4.0 22 Feb 2016 H1 U2 — Yes Details →
0.3.11 14 Feb 2016 H1 U2 — Yes Details →
0.3.10 27 Jan 2016 H1 U2 — Yes Details →
0.3.9 19 Jan 2016 H1 U2 — Yes Details →
0.3.8 22 Nov 2015 H1 U2 — Yes Details →
0.3.7 18 Nov 2015 H1 U2 — Yes Details →
0.3.6 21 Oct 2015 H1 U2 — Yes Details →
0.3.5 19 Oct 2015 H1 U2 — Yes Details →
0.3.4 11 Sep 2015 H1 U2 — Yes Details →
0.3.3 03 Sep 2015 H1 U2 — Yes Details →
0.3.2 01 Aug 2015 H1 U2 — Yes Details →
0.3.1 29 Jul 2015 H1 U2 — Yes Details →
0.3.0 28 Jul 2015 H1 U2 — Yes Details →
0.2.20 22 Jul 2015 H1 U2 — Yes Details →
0.2.19 20 Jul 2015 H1 U2 — Yes Details →
0.2.18 29 Jun 2015 H1 U2 — Yes Details →
0.2.17 17 Jun 2015 H1 U2 — Yes Details →
0.2.16 17 Jun 2015 H1 U2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 2
  • 2024 2

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

03 Vulnerabilities

Recorded vulnerabilities for libgit2-sys

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Memory corruption, denial of service, and arbitrary code execution in libgit2-sys 8.6 high 0.16.2 06 Feb 2024
Memory Corruption, Denial of Service, and Arbitrary Code Execution in libgit2-sys 8.6 high 0.16.2 12 Feb 2024
Vulnerability in libgit2-sys: git2-rs fails to verify SSH keys by default 6.8 medium 0.14.2 20 Jan 2023
CVE-2023-22742: SSH key verification bypass in libgit2-sys N/A unrated 0.13.5 20 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 libgit2-sys

Is libgit2-sys safe to use?

Vulert records 4 vulnerabilities for libgit2-sys in crates.io: 0 critical, 1 high, 1 medium and 0 low, plus 2 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 libgit2-sys's Vulert package health score?

Vulert scores libgit2-sys 66/100, which reads as usable, but worth attention. 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 libgit2-sys affected?

Yes. 0.10.0, the version you would install today, has 3 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of libgit2-sys should I use?

0.10.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 libgit2-sys have?

4 vulnerabilities are recorded for libgit2-sys in the crates.io ecosystem: 0 critical, 1 high, 1 medium and 0 low, plus 2 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 libgit2-sys vulnerabilities disclosed?

0 vulnerabilities were recorded for libgit2-sys in the last 12 months, and the oldest entry in this database dates to 20 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 libgit2-sys 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 libgit2-sys for upcoming vulnerabilities?

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