Vulnerability Database · crates.io · libgit2-sys · Version
libgit2-sys 0.8.1
0.8.1 is affected by 3 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 0.10.0.
Critical 0 High 2 Medium 0 Low 0 Unrated 1
-
Released 17 Jun 2019
Licence Apache-2.0 OR MIT
Also known from other sources 4
Newer releases 152
Database updated 23/Oct/2026
Release and licence data published by crates.io. 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 Vulnerabilities affecting this version
libgit2-sys 0.8.1 vulnerabilities
3 vulnerabilities cover libgit2-sys 0.8.1. Open the full list 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 | 12 Feb 2024 |
| Memory corruption, denial of service, and arbitrary code execution in libgit2-sys | 8.6 high | 0.16.2 | 06 Feb 2024 |
| CVE-2023-22742: SSH key verification bypass in libgit2-sys | N/A unrated | 0.13.5 | 20 Jan 2023 |
Looking for another version, or everything Vulert holds for libgit2-sys?
Questions
About libgit2-sys 0.8.1
Is libgit2-sys 0.8.1 vulnerable?
Yes. 3 vulnerabilities in the Vulert database cover libgit2-sys 0.8.1: 0 critical, 2 high, 0 medium and 0 low, plus 1 not yet rated. The upgrade Vulert recommends is 0.10.0, and each entry above names the fixed version to move to.
Which version of libgit2-sys should I use instead of 0.8.1?
0.10.0 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 0.8.1 the latest release of libgit2-sys?
No. 0.8.1 was published 17 Jun 2019, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
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.