Memory corruption in privoxy
Priority LOW 37CWE-119Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-119 and the CVSS impact.
Summary
A flaw was found in privoxy before 3.0.32. A invalid read of size two may occur in chunked_body_is_complete() leading to denial of service.
Why it matters now
EPSS 0.01953 80th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | privoxy | privoxy 3.0.32 | — | No fix listed | CNA |
- privoxy Vendor— Affected privoxy 3.0.32 Fixed in — No fix listed CNA
Remediation
No fixed version listed by the sources yet.
Vendor assessments
Timeline
- 2026-10-02 Threatist record created from CVE-2021-20275
- 2026-10-03 Alias added: GHSA-xq2j-fg32-wv9c
References
Sources
- CVE-2021-20275 · CVE Program
- CVE-2021-20275 · NVD
- FIRST EPSS
- GHSA-xq2j-fg32-wv9c · GitHub Advisory Database · CC BY 4.0
- CVE-2021-20275 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences