Vulnerability Database · Red Hat · Package report
glibc: vulnerability history, versions and safety
glibc is a package in the Red Hat ecosystem. Vulert records 2 vulnerabilities for it across 2 affected ranges, from Jul 2025 to Aug 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on glibc i
Updated on 23 Oct 2026
Every vulnerability Vulert records for this package has a fix, and the newest was recorded 07 Aug 2025. Apply the fixes listed below and you are clear.
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 2 over 1 year · 0 in the last year i
- Latest disclosure 07 Aug 2025 i
- Highest CVSS 5.6 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
Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.
| Affected range | Vulnerabilities |
|---|---|
| up to 0:2.39-46.el10_0 (exclusive) | 1 |
| up to 0:2.39-43.el10_0 (exclusive) | 1 |
02 Disclosure history
How often vulnerabilities are recorded
Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for glibc
No vulnerabilities match this view. This package does have 2 vulnerabilities recorded — search the database to see them all.
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
Questions
About glibc
Is glibc safe to use?
Vulert records 2 vulnerabilities for glibc in Red Hat: 0 critical, 0 high, 0 medium and 0 low, plus 2 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 glibc have?
2 vulnerabilities are recorded for glibc in the Red Hat ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 2 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 glibc vulnerabilities disclosed?
0 vulnerabilities were recorded for glibc in the last 12 months, and the oldest entry in this database dates to 15 Jul 2025. 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 glibc 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 glibc for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the glibc version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.