VulertSecurity VulertSecurity

Vulnerability Database · Alpine · Package report

privoxy: vulnerability history, versions and safety

privoxy is a package in the Alpine ecosystem. Vulert records 34 vulnerabilities for it across 19 releases, from Mar 2021 to Dec 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
34 vulnerabilities recorded U34
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 privoxy vulnerabilities

Vulert verdict on privoxy i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 34 vulnerabilities on record across 1 year, 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 34 over 1 year · 0 in the last year i
  • Latest disclosure 23 Dec 2021 i
  • Highest CVSS 7.5 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 privoxy, 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.

Newest 19 of 19 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 34

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

03 Vulnerabilities

Recorded vulnerabilities for privoxy

The 5 most severe of 34 vulnerabilities recorded for this package

Search all 34 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Memory Leak in Privoxy show-status CGI Handler (CVE-2021-20210) 7.5 high 3.0.29-r0 25 Mar 2021
Memory Leak Vulnerability in Privoxy 7.5 high 3.0.29-r0 25 Mar 2021
Memory Leak Vulnerability in Privoxy 7.5 high 3.0.29-r0 25 Mar 2021
Denial of Service Vulnerability in Privoxy: CVE-2021-20276 7.5 high 3.0.32-r0 09 Mar 2021
Denial of Service Vulnerability in Privoxy: CVE-2021-20275 7.5 high 3.0.32-r0 09 Mar 2021

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 privoxy

Is privoxy safe to use?

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

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

0 vulnerabilities were recorded for privoxy in the last 12 months, and the oldest entry in this database dates to 09 Mar 2021. 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 privoxy 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 privoxy for upcoming vulnerabilities?

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