Skip to content
Fencer Vulns
critical 9.8

CVE-2002-0059 json

The decompression algorithm in zlib 1.1.3 and earlier, as used in many different utilities and packages, causes inflateEnd to release certa…

published 2002-03-15 24 y ago modified 2026-06-16 4 mo ago also EUVD-2002-0059

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
9.7%
EPSS 9.7% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

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.

Patch / fix

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2002-0059 updated cvss 7.0

zlib: Double free in inflateEnd

  • Red Hat Linux 6.2 Red Hat Linux 7.0 Red Hat Linux 7.1 Red Hat Linux 7.2
    fixed: vendor fix RHSA-2002:026
  • Red Hat Powertools 6.2 Red Hat Powertools 7.0 Red Hat Powertools 7.1
    fixed: vendor fix RHSA-2002:027
  • Red Hat Enterprise Linux 6 zlib, minizip Red Hat Enterprise Linux 7 zlib, minizip Red Hat Enterprise Linux 8 zlib Red Hat Enterprise Linux 9 zlib Red Hat JBoss Enterprise Application Platform 6 zlib Red Hat Software Collections rh-nodejs12-npm, rh-nodejs14-npm, rh-nodejs12-nodejs, rh-nodejs14-nodejs, rh-nodejs14-nodejs-full-i18n
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

9.69% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.