VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

uclibc: vulnerability history, versions and safety

uclibc is a package in the Debian ecosystem. Vulert records 17 vulnerabilities for it across 2 releases, from Jan 2017 to Sep 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
17 vulnerabilities recorded U17
i
11 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 uclibc vulnerabilities

Vulert verdict on uclibc i

Updated on 23 Oct 2026

Careful: 11 of the 17 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 17 vulnerabilities on record across 5 years, none in the last year.

What to do: Plan around the 11 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 17 over 5 years · 0 in the last year i
  • Latest disclosure 29 Sep 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 11 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 uclibc, 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
1.0.54-1 U5 No Details →
1.0.35-1 U11 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 10
  • 2021 2
  • 2022 5

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

03 Vulnerabilities

Recorded vulnerabilities for uclibc

The 5 most severe of 17 vulnerabilities recorded for this package

Search all 17 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Memory Corruption Vulnerability in uClibC 9.8 critical No fix published 29 Sep 2022
Out-of-Bounds Read Vulnerability in uClibc 9.8 critical No fix published 16 Jun 2017
Integer Wrap-around Vulnerability in uClibc-ng 9.8 critical No fix published 03 May 2022
Domain Hijacking and Code Injection in uClibc and uClibc-ng 9.6 critical No fix published 10 Nov 2021
Denial of Service in uClibc-ng 7.5 high 1.0.20-1 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 uclibc

Is uclibc safe to use?

Vulert records 17 vulnerabilities for uclibc in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 17 not yet rated. 11 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does uclibc have?

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

0 vulnerabilities were recorded for uclibc in the last 12 months, and the oldest entry in this database dates to 27 Jan 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 uclibc 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 uclibc for upcoming vulnerabilities?

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