VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

lcms2: vulnerability history, versions and safety

lcms2 is a package in the Debian ecosystem. Vulert records 13 vulnerabilities for it across 7 releases, from Jan 2014 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
13 vulnerabilities recorded U13
i
5 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
2 in the last 12 months

Most recent disclosure 30 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all lcms2 vulnerabilities

Vulert verdict on lcms2 i

Updated on 23 Oct 2026

Careful: 5 of the 13 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 13 vulnerabilities on record across 12 years, 2 in the last year.

What to do: Plan around the 5 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 13 over 12 years · 2 in the last year i
  • Latest disclosure 30 Apr 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 5 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 lcms2, 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
2.17-1 U2 No Details →
2.16-2 U5 No Details →
2.16-1 U5 No Details →
2.14-2 U5 No Details →
2.14-1 U5 No Details →
2.13.1-1 U5 No Details →
2.12~rc1-2 U5 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2014 4
  • 2016 2
  • 2017 1
  • 2018 1
  • 2025 3
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for lcms2

The 5 most severe of 13 vulnerabilities recorded for this package

Search all 13 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Double Free Vulnerability in Little CMS 2 (lcms2) - CVE-2013-7455 9.8 critical 2.6-1 07 May 2016
Critical Vulnerability in lcms2 Package: CVE-2026-41254 N/A unrated No fix published 18 Apr 2026
Out-of-Bounds Heap Read Vulnerability in Little CMS (lcms2) N/A unrated 2.8-4 03 Feb 2017
Integer Overflow Vulnerability in Little CMS 2.9 - Heap-Based Buffer Overflow Risk N/A unrated 2.9-3 04 Sep 2018
Heap Buffer Overflow Vulnerability in lcms2 Package N/A unrated No fix published 01 Apr 2025

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 lcms2

Is lcms2 safe to use?

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

How many vulnerabilities does lcms2 have?

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

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

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