VulnSea

gnu has 190 CVEs on record between 2015 and 2026. Disclosure cadence is accelerating: 25 in the last 90 days against 8 in the 90 before. The busiest recent month was September 2026 with 16. The median CVSS is 6.5 (medium), with 13 rated critical. 1% have been exploited in the wild, in line with the corpus average. The dominant weakness classes are CWE-787 (39) and CWE-476 (25). Most affected products: binutils (48), glibc (36), LibreDWG (24).

CVEs per month

Last 12 months, by publish date

120102030405060708091011
Exploited share
1% vs 1% corpus
Median CVSS
6.5
Publish → KEV
—(2)
Last 90 days
25 prev 8

Products

  • binutils 48
  • glibc 36
  • LibreDWG 24
  • gnutls 20
  • grub2 15
  • tar 7
190
Total CVEs
13
Critical
2
CISA KEV
2
Exploited

gnu vulnerabilities

CVEs affecting gnu, newest first. Open any entry for full detail, references, and exploit status.

190 CVEsRSS

CVE-2019-9923High· 7.5PoC
7y ago

pax_decode_header in sparse.c in GNU Tar before 1.32 had a NULL pointer dereference when parsing certain archives that have malformed extended headers.

pax_decode_header in sparse.c in GNU Tar before 1.32 had a NULL pointer dereference when parsing certain archives that have malformed extended headers.

▾ Midnightgnu · tarEPSS 3.2%via NVD
CVE-2019-9169Critical· 9.8⚖ disputed
7y ago

In the GNU C Library (aka glibc or libc6) through 2.29, proceed_next_node in posix/regexec.c has a heap-based buffer over-read via an attempted case-insensitive regular-expression match.

In the GNU C Library (aka glibc or libc6) through 2.29, proceed_next_node in posix/regexec.c has a heap-based buffer over-read via an attempted case-insensitive regular-expression match.

▾ Midnightgnu · glibcEPSS 4.7%via NVD
CVE-2019-7309Medium· 5.5⚖ disputed
7y ago

In the GNU C Library (aka glibc or libc6) through 2.29, the memcmp function for the x32 architecture can incorrectly return zero (indicating that the inputs are equal) because the RDX most significant bit is mishandled.

In the GNU C Library (aka glibc or libc6) through 2.29, the memcmp function for the x32 architecture can incorrectly return zero (indicating that the inputs are equal) because the RDX most significant bit is mishandled.

▾ Sunlitgnu · glibcEPSS 0.61%via NVD
CVE-2016-10739Medium· 5.3
7y ago

In the GNU C Library (aka glibc or libc6) through 2.28, the getaddrinfo function would successfully parse a string that contained an IPv4 address followed by whitespace and arbitrary characters, which could lead applications to incorrect…

In the GNU C Library (aka glibc or libc6) through 2.28, the getaddrinfo function would successfully parse a string that contained an IPv4 address followed by whitespace and arbitrary characters, which could lead applications to incorrect…

▾ Sunlitgnu · glibcEPSS 0.48%via NVD
CVE-2019-6488High· 7.8⚖ disputed
7y ago

The string component in the GNU C Library (aka glibc or libc6) through 2.28, when running on the x32 architecture, incorrectly attempts to use a 64-bit register for size_t in assembly codes, which can lead to a segmentation fault or poss…

The string component in the GNU C Library (aka glibc or libc6) through 2.28, when running on the x32 architecture, incorrectly attempts to use a 64-bit register for size_t in assembly codes, which can lead to a segmentation fault or poss…

▾ Twilightgnu · glibcEPSS 0.45%via NVD
CVE-2018-20482Medium· 4.7
7y ago

GNU Tar through 1.30, when --sparse is used, mishandles file shrinkage during read access, which allows local users to cause a denial of service (infinite read loop in sparse_dump_region in sparse.c) by modifying a file that is supposed …

GNU Tar through 1.30, when --sparse is used, mishandles file shrinkage during read access, which allows local users to cause a denial of service (infinite read loop in sparse_dump_region in sparse.c) by modifying a file that is supposed …

▾ Sunlitgnu · tarEPSS 0.53%via NVD
CVE-2018-19591High· 7.5PoC
7y ago

In the GNU C Library (aka glibc or libc6) through 2.28, attempting to resolve a crafted hostname via getaddrinfo() leads to the allocation of a socket descriptor that is not closed

In the GNU C Library (aka glibc or libc6) through 2.28, attempting to resolve a crafted hostname via getaddrinfo() leads to the allocation of a socket descriptor that is not closed. This is related to the if_nametoindex() function.

▾ Midnightgnu · glibcEPSS 5.5%via NVD
CVE-2018-18700Medium· 5.5
8y ago

An issue was discovered in cp-demangle.c in GNU libiberty, as distributed in GNU Binutils 2.31

An issue was discovered in cp-demangle.c in GNU libiberty, as distributed in GNU Binutils 2.31. There is a stack consumption vulnerability resulting from infinite recursion in the functions d_name(), d_encoding(), and d_local_name() in c…

▾ Sunlitgnu · binutilsEPSS 1.7%via NVD
CVE-2016-10228Medium· 5.9
9y ago

The iconv program in the GNU C Library (aka glibc or libc6) 2.31 and earlier, when invoked with multiple suffixes in the destination encoding (TRANSLATE or IGNORE) along with the -c option, enters an infinite loop when processing invalid…

The iconv program in the GNU C Library (aka glibc or libc6) 2.31 and earlier, when invoked with multiple suffixes in the destination encoding (TRANSLATE or IGNORE) along with the -c option, enters an infinite loop when processing invalid…

▾ Sunlitgnu · glibcEPSS 4.1%via NVD
CVE-2015-1197Low· 1.9
11y ago

cpio 2.11, when using the --no-absolute-filenames option, allows local users to write to arbitrary files via a symlink attack on a file in an archive.

cpio 2.11, when using the --no-absolute-filenames option, allows local users to write to arbitrary files via a symlink attack on a file in an archive.

▾ Sunlitgnu · cpioEPSS 2.9%via NVD
gnu vulnerabilities (CVEs) — page 7 · VulnSea