VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

libgit2: vulnerability history, versions and safety

libgit2 is a package in the OSS-Fuzz ecosystem. Vulert records 11 vulnerabilities for it across 4 releases, from Jul 2020 to Feb 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
11 vulnerabilities recorded M11
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 vulnerabilities

Vulert verdict on libgit2 i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 18 Feb 2023. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 11 vulnerabilities on record across 2 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 11 over 2 years · 0 in the last year i
  • Latest disclosure 18 Feb 2023 i
  • Highest CVSS n/a i
  • With no published fix 0 i

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 holds for libgit2, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
v1.6.4 M2 Yes Details →
v1.6.3 M2 Yes Details →
v1.6.2 M2 Yes Details →
v1.6.1 M2 Yes Details →

Newest 4 of 4 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 2
  • 2021 7
  • 2023 2

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

03 Vulnerabilities

Recorded vulnerabilities for libgit2

The 5 most severe of 11 vulnerabilities recorded for this package

Search all 11 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-buffer-overflow in libgit2: git__strntol64 N/A medium 4209a5125802e714a6342a74ff0835c5c4a2397d 13 Jan 2021
Heap-buffer-overflow in prefixcmp in libgit2 N/A medium cb23c3efd22d34db279ceb39cc312473761db5ed 13 Jan 2021
Heap-buffer-overflow in libgit2: git_buf_vprintf N/A medium bea65980c7a42e34edfafbdc40b199ba7b2a564e 12 Jan 2021
Heap-buffer-overflow in parse_mode in libgit2 N/A medium f647bbc88d243a81d8771ba2fd1c346c34a3d9d7 13 Jan 2021
Heap-buffer-overflow in libgit2 N/A medium 52f859fd534e3c16c2c03b9a2375f00a50f3996e 12 Jan 2021

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

Is libgit2 safe to use?

Vulert records 11 vulnerabilities for libgit2 in OSS-Fuzz: 0 critical, 0 high, 11 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.

How many vulnerabilities does libgit2 have?

11 vulnerabilities are recorded for libgit2 in the OSS-Fuzz ecosystem: 0 critical, 0 high, 11 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 libgit2 vulnerabilities disclosed?

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

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