All vulnerabilities
CVE-2026-61642GHSA-537g-4gfh-w7m6

Squid Request Smuggling in HTTP Transfer-Encoding

squid-cache squid
CVSS
7.7High
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)4.68%Chance of exploitation activity in the next 30 days, higher than 91% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in7.6Fixed versionGitHub
Published13 Oct 2026Updated 13 Oct 2026CVE List

What fixes it

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Description

Squid is a caching proxy for the Web. From 3.3.0.1 to before 7.6, due to an improper enforcement of behavioral workflow bug, Squid is vulnerable to a Request Smuggling attack against HTTP/1.1 Transfer-Encoding. HTTP header parsing (src/HttpHeader.cc) accepted the bare Transfer-Encoding: identity form, which the HTTP specification prohibits because any transfer coding must be wrapped within chunked encoding. This problem allows a trusted client to perform an HTTP Request Smuggling attack when HTTP/1.1 is used, bypassing security mechanisms that may be in place between attacker and Squid. When there is an HTTP cache operating prior to the affected Squid, this Request Smuggling attack also allows the attacker to poison that web cache and store arbitrary malicious content at any URL for delivery to other clients' future requests. This issue is fixed in version 7.6.

Text from CVE List

Affected versions 2

  • squidaffected: >= 3.3.0.1, < 7.6CVE List
  • squid3.3.0.1-7.5GitHub

References 6