Generated remediation guidance and an executive summary. No account required.
An issue was discovered in Squid before 4.13 and 5.x before 5.0.4. Due to incorrect data validation, HTTP Request Splitting attacks may succeed against HTTP and HTTPS traffic. This leads to cache poisoning. This allows any client, including browser scripts, to bypass local security and poison the browser cache and any downstream caches with content from an arbitrary source. Squid uses a string search instead of parsing the Transfer-Encoding header to find chunked encoding. This allows an attacker to hide a second request inside Transfer-Encoding: it is interpreted by Squid as chunked and split out into a second request delivered upstream. Squid will then deliver two distinct responses to the client, corrupting any downstream caches.
Cite this page
CVE-2020-15811. CVEDatabase.com. Retrieved 1 May 2026. https://cvedatabase.com/cve/CVE-2020-15811
Use CWE-697, Squid-Cache vendor hub and Squid product page to widen CVE-2020-15811 into its surrounding weakness, vendor, and product context.
Compare it with CVE-2025-62168, CVE-2025-54574 and CVE-2026-33526 for nearby disclosures in the same product family.