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 Smuggling 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 proxy cache and any downstream caches with content from an arbitrary source. When configured for relaxed header parsing (the default), Squid relays headers containing whitespace characters to upstream servers. When this occurs as a prefix to a Content-Length header, the frame length specified will be ignored by Squid (allowing for a conflicting length to be used from another Content-Length header) but relayed upstream.
Cite this page
CVE-2020-15810. CVEDatabase.com. Retrieved 1 May 2026. https://cvedatabase.com/cve/CVE-2020-15810
Use CWE-444, Squid-Cache vendor hub and Squid product page to widen CVE-2020-15810 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.