VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

icu: vulnerability history, versions and safety

icu is a package in the Debian ecosystem. Vulert records 64 vulnerabilities for it across 1 release, from Jan 2008 to Jun 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
64 vulnerabilities recorded U64
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 icu vulnerabilities

Vulert verdict on icu i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 64 vulnerabilities on record across 17 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 64 over 17 years · 0 in the last year i
  • Latest disclosure 15 Jun 2025 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 icu, 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
67.1-7 U2 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

  • 2008 6
  • 2009 2
  • 2012 2
  • 2013 12
  • 2015 22
  • 2016 4
  • 2017 8
  • 2018 4
  • 2020 1
  • 2021 1
  • 2025 2

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

03 Vulnerabilities

Recorded vulnerabilities for icu

The 5 most severe of 64 vulnerabilities recorded for this package

Search all 64 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Denial of Service Vulnerability in ICU Regular Expressions Package 9.8 critical 52.1-7.1 24 Apr 2017
Critical Buffer Overflow Vulnerability in ICU Package - CVE-2014-9911 9.8 critical 55.1-3 04 Jan 2017
Critical Double Free Vulnerability in ICU Package Allows Remote Code Execution 9.8 critical 57.1-7 16 Oct 2017
Integer Overflow Vulnerability in ICU Package: CVE-2018-18928 9.8 critical 63.1-3 04 Nov 2018
Integer Overflow Vulnerability in ICU Package - CVE-2017-15422 6.5 medium 57.1-9 28 Aug 2018

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 icu

Is icu safe to use?

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

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

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

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