Skip to content
Fencer Intel
medium 6.5

CVE-2018-8098 json

Integer overflow in the index.c:read_entry() function while decompressing a compressed prefix length in libgit2 before v0.26.2 allows an at…

published 2018-03-14 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-19774

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 73%
public exploits
0
none known

Summary

Integer overflow in the index.c:read_entry() function while decompressing a compressed prefix length in libgit2 before v0.26.2 allows an attacker to cause a denial of service (out-of-bounds read) via a crafted repository index file.

Patch / fix

  • libgit2 libgit2 0.26.2
  • libgit2 Debian 14, Debian 13, Debian 12 0.27.0+dfsg.1-0.6

debian advisories DEBIAN-CVE-2018-8098

  • libgit2 Ubuntu Pro 18.04 LTS 0.26.0+dfsg.1-1.1ubuntu0.2+esm2

ubuntu advisories UBUNTU-CVE-2018-8098

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • libgit2 openSUSE Tumbleweed 1.1.1-1.2

opensuse advisories openSUSE-SU-2024:10943-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-8098 updated cvss 4.3

libgit2: denial of service (DoS) via crafted repository index files

  • Red Hat Enterprise Linux 8 libgit2
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.43% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-190 Integer Overflow or Wraparound

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.