VulertSecurity VulertSecurity

Vulnerability Database · Ubuntu · Package report

libgit2: vulnerability history, versions and safety

libgit2 is a package in the Ubuntu ecosystem. Vulert records 15 vulnerabilities for it across 3 releases, from Feb 2017 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
15 vulnerabilities recorded U15
i
12 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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

Careful: 12 of the 15 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 15 vulnerabilities on record across 7 years, none in the last year.

What to do: Plan around the 12 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 15 over 7 years · 0 in the last year i
  • Latest disclosure 06 Feb 2024 i
  • Highest CVSS 9.8 i
  • With no published fix 12 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
0.19.0-2 U15 No Details →
0.19.0-2ubuntu0.4 U15 No Details →
0.19.0-2ubuntu0.4+esm1 U12 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 7
  • 2018 3
  • 2020 2
  • 2021 1
  • 2023 1
  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for libgit2

The 5 most severe of 15 vulnerabilities recorded for this package

Search all 15 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Buffer Overflow Vulnerability in libgit2 Package 9.8 critical No fix published 24 Mar 2017
Critical Remote Code Execution Vulnerability in libgit2: CVE-2020-12278 9.8 critical No fix published 27 Apr 2020
Critical Remote Code Execution Vulnerability in libgit2: CVE-2020-12279 9.8 critical No fix published 27 Apr 2020
Heap Corruption Vulnerability in libgit2: Potential for Arbitrary Code Execution 8.6 high No fix published 06 Feb 2024
Denial of Service Vulnerability in libgit2: CVE-2016-10129 7.5 high No fix published 24 Mar 2017

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 15 vulnerabilities for libgit2 in Ubuntu: 0 critical, 0 high, 0 medium and 0 low, plus 15 not yet rated. 12 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does libgit2 have?

15 vulnerabilities are recorded for libgit2 in the Ubuntu ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 15 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.