CVE-2008-0888

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week

Also known asEUVD-2008-0895 (ENISA EUVD) · GHSA-q7mr-xjvc-chw3 (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 6.3%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The NEEDBITS macro in the inflate_dynamic function in inflate.c for unzip can be invoked using invalid buffers, which allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via unknown vectors that trigger a free of uninitialized or previously-freed data.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
6.3%
EPSS %ILE
93rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
6.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 17, 2008

Last Modified

August 26, 2025

References (31)

15 of 31 shown · show the other 16

Vendor Advisories for CVE-2008-0888(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuunzip (5.52-9ubuntu3.1) @ feisty2026-11-01ubuntu
redhatunzip-0:5.50-36.EL32008-03-18redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
unzip—
  • every version up to 5.52-11: fixed in 5.52-11
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
unzip—
  • every version up to 5.52-11: fixed in 5.52-11
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
unzip—
  • every version up to 5.52-11: fixed in 5.52-11
—
Debian:3.1(1)
PackageVulnerable rangeFix by version rangeDependents
unzip5.52-1, 5.52-1sarge1, 5.52-1sarge2, 5.52-1sarge3, 5.52-1sarge4
  • every version up to 5.52-1sarge5: fixed in 5.52-1sarge5
—
Debian:4.0(1)
PackageVulnerable rangeFix by version rangeDependents
unzip5.52-9
  • every version up to 5.52-9etch1: fixed in 5.52-9etch1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-02 16:28 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  2. 2026-11-01 17:51 UTCEG score recompute
  3. 2026-11-01 17:51 UTCVendor advisory
  4. 2026-11-01 17:51 UTCGHSA enrichmentGHSA-q7mr-xjvc-chw3 · GitHub severity HIGH
  5. 2026-11-01 16:25 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  6. 2026-10-31 16:25 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  7. 2026-10-30 16:26 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  8. 2026-10-29 16:25 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  9. 2026-10-28 16:25 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  10. 2026-10-27 16:25 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  11. 2026-10-26 16:25 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  12. 2026-10-26 11:25 UTCOSV refresh
  13. 2026-10-25 20:31 UTCEG score recompute
  14. 2026-10-25 16:25 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  15. 2026-10-24 16:25 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  16. 2026-10-23 16:25 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  17. 2026-10-22 16:25 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  18. 2026-10-21 16:25 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  19. 2026-10-20 16:25 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  20. 2026-10-19 16:25 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  21. 2026-10-18 16:25 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  22. 2026-10-18 11:53 UTCEG score recompute
  23. 2026-10-17 16:25 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  24. 2026-10-16 16:25 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  25. 2026-10-15 16:25 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
Show 16 more
  1. 2026-10-14 16:25 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  2. 2026-10-13 16:25 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  3. 2026-10-12 21:54 UTCEG score recompute
  4. 2026-10-12 16:26 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  5. 2026-10-12 02:02 UTCEG score recompute
  6. 2026-10-11 13:37 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  7. 2026-10-10 19:53 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  8. 2026-10-09 20:00 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  9. 2026-10-08 16:33 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  10. 2026-10-07 23:37 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  11. 2026-10-06 15:09 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  12. 2026-10-05 17:37 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  13. 2026-10-04 23:15 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  14. 2026-10-04 09:08 UTCEG score recompute
  15. 2026-10-04 09:08 UTCVendor advisory
  16. 2026-10-04 09:07 UTCGHSA enrichmentGHSA-q7mr-xjvc-chw3 · GitHub severity HIGH

Related CVEs(same product + same CWE)

Frequently asked(4)

What is CVE-2008-0888?
CVE-2008-0888 is a vulnerability whose severity is not yet rated; its CVE record was published on March 17, 2008. The NEEDBITS macro in the inflate_dynamic function in inflate.c for unzip can be invoked using invalid buffers, which allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via unknown vectors that trigger a free of uninitialized or previously-freed data.
When was CVE-2008-0888 made public?
CVE-2008-0888 was made public on March 17, 2008: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on March 17, 2008. EchelonGraph's copy of the record carries a last-modified date of August 26, 2025; the record at its source may have been updated since.
Is CVE-2008-0888 actively exploited?
CVE-2008-0888 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.3% probability of exploitation in the next 30 days (93rd percentile of EPSS-scored CVEs).
How do I remediate CVE-2008-0888?
A fix for CVE-2008-0888 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2008-0888 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2008-0888

Explore →

Is Your Infrastructure Affected by CVE-2008-0888?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs