VulertSecurity VulertSecurity

Vulnerability Database · Alpine · Package report

libgit2: vulnerability history, versions and safety

libgit2 is a package in the Alpine ecosystem. Vulert records 16 vulnerabilities for it across 20 releases, from Feb 2017 to Aug 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
16 vulnerabilities recorded U16
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 Aug 2018. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 16 vulnerabilities on record across 1 year, 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 16 over 1 year · 0 in the last year i
  • Latest disclosure 18 Aug 2018 i
  • Highest CVSS 9.8 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.

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 10
  • 2018 6

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

03 Vulnerabilities

Recorded vulnerabilities for libgit2

The 5 most severe of 16 vulnerabilities recorded for this package

Search all 16 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Buffer Overflow Vulnerability in libgit2 9.8 critical 0.25.1-r0 24 Mar 2017
Critical Buffer Overflow Vulnerability in libgit2: CVE-2016-10128 9.8 critical 0.25.1-r0 24 Mar 2017
Integer Overflow Vulnerability in libgit2 Leading to Potential Memory Leak and Denial of Service 8.1 high 0.27.3-r0 10 Jul 2018
Integer Overflow in libgit2 before 0.27.3 8.1 high 0.27.3-r0 10 Jul 2018
Out-of-Bounds Read Vulnerability in libgit2: CVE-2018-15501 7.5 high 0.27.4-r0 18 Aug 2018

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 16 vulnerabilities for libgit2 in Alpine: 0 critical, 0 high, 0 medium and 0 low, plus 16 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.

How many vulnerabilities does libgit2 have?

16 vulnerabilities are recorded for libgit2 in the Alpine ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 16 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 vulnerabilities disclosed?

0 vulnerabilities were recorded for libgit2 in the last 12 months, and the oldest entry in this database dates to 03 Feb 2017. 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.