VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

eglibc: vulnerability history, versions and safety

eglibc is a package in the Debian ecosystem. Vulert records 7 vulnerabilities for it across 12 releases, from Jul 2014 to Jun 2017. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded U7
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 eglibc vulnerabilities

Vulert verdict on eglibc i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 7 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 7 over 2 years · 0 in the last year i
  • Latest disclosure 19 Jun 2017 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 eglibc, 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 12 of 12 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2014 2
  • 2015 2
  • 2016 2
  • 2017 1

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

03 Vulnerabilities

Recorded vulnerabilities for eglibc

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
eglibc - Stack-based Buffer Overflow in glob Implementation N/A unrated 2.13-38+deb7u11 29 May 2016
eglibc - Stack Clash Vulnerability N/A unrated 2.13-38+deb7u12 19 Jun 2017
eglibc - Security Update N/A unrated 2.13-38+deb7u3 10 Jul 2014
eglibc - Heap-based Buffer Overflow in Transliteration Module Loading Code N/A unrated 2.13-38+deb7u4 26 Aug 2014
eglibc - Buffer Overflow and Command Execution Vulnerabilities N/A unrated 2.13-38+deb7u7 27 Jan 2015

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 eglibc

Is eglibc safe to use?

Vulert records 7 vulnerabilities for eglibc in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 7 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 eglibc have?

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

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

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