VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

imlib2: vulnerability history, versions and safety

imlib2 is a package in the Debian ecosystem. Vulert records 42 vulnerabilities for it across 1 release, from Dec 2004 to Feb 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
42 vulnerabilities recorded U42
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 imlib2 vulnerabilities

Vulert verdict on imlib2 i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 42 vulnerabilities on record across 19 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 42 over 19 years · 0 in the last year i
  • Latest disclosure 09 Feb 2024 i
  • Highest CVSS 9.8 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 imlib2, 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.7.1-2 U6 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2004 2
  • 2005 2
  • 2006 8
  • 2008 4
  • 2009 2
  • 2016 16
  • 2020 2
  • 2024 6

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

03 Vulnerabilities

Recorded vulnerabilities for imlib2

The 5 most severe of 42 vulnerabilities recorded for this package

Search all 42 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
Critical Integer Overflow Vulnerability in imlib2 Package 9.8 critical 1.4.8-1 13 May 2016
Integer Overflow Vulnerability in imlib2 Package Leading to Memory Issues 9.1 critical 1.6.1-2 09 May 2020
Heap Buffer Overflow in imlib2: Critical Vulnerability Detected 8.8 high 1.7.1-2+deb11u1 09 Feb 2024
Heap Buffer Overflow in imlib2 - CVE-2024-25448 8.8 high 1.7.1-2+deb11u1 09 Feb 2024
Memory Allocation Mismanagement in imlib2 - CVE-2024-25450 8.8 high 1.7.1-2+deb11u1 09 Feb 2024

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 imlib2

Is imlib2 safe to use?

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

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

0 vulnerabilities were recorded for imlib2 in the last 12 months, and the oldest entry in this database dates to 31 Dec 2004. 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 imlib2 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 imlib2 for upcoming vulnerabilities?

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