Skip to content
Fencer Vulns
high 7.5

CVE-2021-20209 json

A memory leak vulnerability was found in Privoxy before 3.0.29 in the show-status CGI handler when no action files are configured.

published 2021-05-25 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-7652

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

Summary

A memory leak vulnerability was found in Privoxy before 3.0.29 in the show-status CGI handler when no action files are configured.

Patch / fix

  • privoxy privoxy 3.0.29
  • privoxy Debian 14, Debian 13, Debian 12 3.0.29-1

debian advisories DEBIAN-CVE-2021-20209

  • privoxy Ubuntu 16.04 LTS 3.0.24-1ubuntu0.1
  • privoxy Ubuntu 18.04 LTS 3.0.26-5ubuntu0.1
  • privoxy Ubuntu 20.04 LTS 3.0.28-2ubuntu0.1
  • privoxy Ubuntu Pro 14.04 LTS 3.0.21-7+deb8u1ubuntu0.1~esm1

ubuntu advisories UBUNTU-CVE-2021-20209

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

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-2021-20209 updated cvss 5.9

privoxy: memory leak in the show-status CGI handler when no action files are configured

  • Red Hat All currently supported Red Hat products
    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

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

CVSS scores

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

Affected products

  • n/a privoxy

Classification

Weakness
  • CWE-401 Missing Release of Memory after Effective Lifetime

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.