On this page (7 sections)
Ubuntu has published notice USN-9146-1 for Privoxy, the filtering web proxy. It covers two flaws: a memory leak that could be abused to exhaust resources (CVE-2021-44540) and a cross-site scripting (XSS) issue in error pages (CVE-2021-44543).
If you run Privoxy on an Ubuntu server, a gateway or a developer workstation, the practical step is to check your installed version and apply the update Ubuntu provides. Both CVE records themselves date from December 2021, so the upstream fixes have existed for some time.
What happened
Ubuntu's notice credits two researchers. Joshua Rogers is credited with finding that Privoxy mishandled memory allocation, causing a memory leak, and Artem Ivanov with finding that template names were not properly encoded in error pages (Ubuntu USN-9146-1). The notice is dated November 17, 2026.
The underlying CVE records were published by the National Vulnerability Database on December 23, 2021, and mirrored in the GitHub Advisory Database the next day (GHSA-c56j-2h63-6488, GHSA-hf3j-m5fx-q82c).
Technical details
CVE-2021-44540: memory leak in get_url_spec_param()
The record says the bug was fixed in get_url_spec_param() by freeing the memory of a compiled pattern spec before bailing out. In plain terms, when the function hit an error path, it left allocated memory behind. Repeated over time, leaked memory is never returned, so the process grows. Ubuntu states an attacker could possibly use this to make Privoxy consume excessive resources, leading to denial of service. The record carries a CVSS score of 7.5 (High). The GitHub advisory lists an EPSS score of 1.383%, an estimate of exploitation probability within 30 days.
CVE-2021-44543: XSS in cgi_error_no_template()
The record says the fix encodes the template name in cgi_error_no_template(), and that this applies when Privoxy is configured to serve the user manual itself. XSS happens when user-controlled input is placed into a web page without being neutralized, so a crafted link could run script in a victim's browser in the context of the proxy's page. Ubuntu describes it as something a remote attacker could possibly use for cross-site scripting. The CVSS score is 6.1 (Medium), and the EPSS score is 0.796%.
Who is affected
- Ubuntu systems with the privoxy package installed, which is what USN-9146-1 addresses.
- Anyone exposing Privoxy beyond localhost, since the denial of service concern involves a remote attacker. The research does not detail the exact attack conditions, so treat any reachable instance as in scope.
- For the XSS issue, instances configured to serve the Privoxy user manual themselves, per the CVE description.
- Other distributions and appliances that bundle Privoxy may carry the same code. Check their own advisories, as this research covers only Ubuntu.
How to check your exposure
This read-only command shows whether the privoxy package is installed and which version (Debian/Ubuntu). If the installed version shows as none, there is nothing to patch on this host.
apt-cache policy privoxyThis read-only command shows whether the service is running and, if so, since when (systemd hosts). A very large memory footprint on a long-running process is worth a look.
systemctl status privoxyTo see which addresses Privoxy listens on, search its configuration for the listen-address setting. Seeing only a loopback address means it is not directly reachable from other machines.
grep -n "^listen-address" /etc/privoxy/configWhat to do now
- Read the Ubuntu notice USN-9146-1 and confirm which of your Ubuntu releases it covers.
- Run apt-cache policy privoxy to see whether Privoxy is installed and which version.
- Update the package using your normal update process (commands below).
- Restart Privoxy if the update did not do so, then confirm the service is healthy.
- Limit the listen-address to the interfaces that need it, and firewall the proxy port from untrusted networks.
- If you do not use Privoxy, remove it rather than leaving an unused service installed.
This updates only the privoxy package to the latest version your configured Ubuntu repositories offer.
sudo apt update && sudo apt install --only-upgrade privoxyAfter updating, restart the service and re-run the status check to confirm it is active.
sudo systemctl restart privoxyDetection and monitoring
The memory leak shows up as slow growth in the Privoxy process size, so track its memory use on any host where it runs and alert on steady climbs or unexpected restarts by the out-of-memory killer. For the XSS issue, review proxy logs for requests to unusual or malformed template-related URLs on the Privoxy web interface, and avoid serving the user manual from the proxy unless you need to.
If Privoxy sits in front of internal web tools, keep the rest of the stack in view too. The Webforta security headers checker can show whether pages you control send protective headers such as a content security policy, which limits the impact of script injection bugs in general, and uptime monitoring will flag a proxy that has been knocked over by resource exhaustion.
What we do not know
- Fixed package versions per Ubuntu release are not stated in the research.
- No exploitation in the wild is reported in the sources, and neither CVE appears in CISA KEV there.
- The reason a 2021 CVE pair has a November 2026 Ubuntu notice is not explained in the sources.
For more security advisories and analysis, browse the Webforta blog.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
