CVE-2002-0059

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 28.5%, top 3% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 10%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

The decompression algorithm in zlib 1.1.3 and earlier, as used in many different utilities and packages, causes inflateEnd to release certain memory more than once (a "double free"), which may allow local and remote attackers to execute arbitrary code via a block of malformed compression data.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
94.9%
KEV
Not listed

Published

March 15, 2002

Last Modified

June 16, 2026

Advisory Details (4)

Auto-updated Jun 23, 2026
No patch confirmed yet. Sources: cert.
cert

VU#368819 - Double Free Bug in zlib Compression Library Corrupts malloc's Internal Data Structures

http://www.kb.cert.org/vuls/id/368819
generic

Debian -- The Universal Operating System

http://www.debian.org/security/2002/dsa-122
generic

Online Casinos Canada 2026 - Best Sites to Play for Real Money

http://frontal2.mandriva.com/security/advisories?name=MDKSA-2002:022

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2002-03-11redhat
redhatpatch2002-03-11redhat

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.

Weakness Classification(1)

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

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 2× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-11 08:22 UTCEPSS rescore
  2. 2026-07-08 15:08 UTCEPSS rescore
  3. 2026-07-04 06:26 UTCEPSS rescore
  4. 2026-07-02 14:00 UTCEPSS rescore
  5. 2026-06-27 03:04 UTCEPSS rescore
  6. 2026-06-24 14:01 UTCEPSS rescore
  7. 2026-06-23 21:29 UTCEPSS rescore
  8. 2026-06-22 14:22 UTCEPSS rescore
  9. 2026-06-19 19:22 UTCEPSS rescore
  10. 2026-06-18 17:49 UTCEPSS rescore
  11. 2026-06-18 17:49 UTCEPSS rescore
  12. 2026-06-17 17:49 UTCEPSS rescore
  13. 2026-06-16 17:49 UTCEPSS rescore
  14. 2026-06-14 23:13 UTCEPSS rescore
  15. 2026-06-13 22:56 UTCEPSS rescore
  16. 2026-06-12 23:07 UTCEPSS rescore
  17. 2026-06-11 13:55 UTCEPSS rescore
  18. 2026-06-10 22:13 UTCEPSS rescore
  19. 2026-06-10 13:17 UTCEPSS rescore
  20. 2026-06-08 14:13 UTCEPSS rescore
  21. 2026-06-06 13:44 UTCEPSS rescore
  22. 2026-06-04 13:09 UTCEPSS rescore
  23. 2026-06-02 20:10 UTCEPSS rescore
  24. 2026-06-01 13:48 UTCEPSS rescore
  25. 2026-05-31 22:27 UTCEPSS rescore
Show 44 more
  1. 2026-05-31 00:13 UTCEPSS rescore
  2. 2026-05-31 00:13 UTCEPSS rescore
  3. 2026-05-29 13:40 UTCEPSS rescore
  4. 2026-05-28 13:42 UTCEPSS rescore
  5. 2026-05-28 13:42 UTCEPSS rescore
  6. 2026-05-28 13:42 UTCEPSS rescore
  7. 2026-05-28 13:42 UTCEPSS rescore
  8. 2026-05-27 13:37 UTCEPSS rescore
  9. 2026-05-27 13:37 UTCEPSS rescore
  10. 2026-05-26 13:41 UTCEPSS rescore
  11. 2026-05-26 13:41 UTCEPSS rescore
  12. 2026-05-26 13:41 UTCEPSS rescore
  13. 2026-05-24 16:42 UTCEPSS rescore
  14. 2026-05-23 00:10 UTCEG score recompute
  15. 2026-05-22 21:15 UTCEPSS rescore
  16. 2026-05-20 22:36 UTCEPSS rescore
  17. 2026-05-20 11:20 UTCEPSS rescore
  18. 2026-05-20 11:20 UTCEPSS rescore
  19. 2026-05-20 07:48 UTCEG score recompute
  20. 2026-05-20 07:48 UTCVendor advisory
  21. 2026-05-20 07:48 UTCGHSA enrichment
  22. 2026-05-20 03:37 UTCEG score recompute
  23. 2026-05-20 03:37 UTCVendor advisory
  24. 2026-05-20 03:37 UTCGHSA enrichment
  25. 2026-05-19 23:16 UTCEG score recompute
  26. 2026-05-19 23:16 UTCVendor advisory
  27. 2026-05-19 23:16 UTCGHSA enrichment
  28. 2026-05-19 19:02 UTCEG score recompute
  29. 2026-05-19 19:02 UTCVendor advisory
  30. 2026-05-19 19:02 UTCGHSA enrichment
  31. 2026-05-19 14:48 UTCEG score recompute
  32. 2026-05-19 14:48 UTCVendor advisory
  33. 2026-05-19 14:48 UTCGHSA enrichment
  34. 2026-05-19 10:33 UTCEG score recompute
  35. 2026-05-19 10:33 UTCVendor advisory
  36. 2026-05-19 10:33 UTCGHSA enrichment
  37. 2026-05-19 06:17 UTCEG score recompute
  38. 2026-05-19 06:17 UTCVendor advisory
  39. 2026-05-19 06:16 UTCGHSA enrichment
  40. 2026-05-19 02:05 UTCEG score recompute
  41. 2026-05-19 02:05 UTCVendor advisory
  42. 2026-05-19 02:05 UTCGHSA enrichment
  43. 2026-05-18 21:29 UTCEPSS rescore
  44. 2026-05-18 21:29 UTCEPSS rescore

Frequently asked(5)

What is CVE-2002-0059?
CVE-2002-0059 is a critical vulnerability published on March 15, 2002. The decompression algorithm in zlib 1.1.3 and earlier, as used in many different utilities and packages, causes inflateEnd to release certain memory more than once (a "double free"), which may allow local and remote attackers to execute arbitrary code via a block of malformed compression data.
When was CVE-2002-0059 disclosed?
CVE-2002-0059 was first published in the National Vulnerability Database on March 15, 2002, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2002-0059 actively exploited?
CVE-2002-0059 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 94.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2002-0059?
CVE-2002-0059 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2002-0059?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2002-0059, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2002-0059

Explore →

Is Your Infrastructure Affected by CVE-2002-0059?

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