cve.bz

CVE-2026-61642 squid-cache squid: HTTP Request Smuggling

7.7 highEPSS 2.0%

High (7.7) in squid-cache squid. EPSS 2.0% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.7 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
EPSS
2.0% (unchanged from 2.0% a week ago; 4.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 81st percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-444 Inconsistent Interpretation of HTTP Requests (HTTP Request Smuggling)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-61642 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-61642?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-61642?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-61642 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-61642

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-61642](https://cve.bz/cve/badge/CVE-2026-61642.svg)](https://cve.bz/cve/CVE-2026-61642)

HTML:

<a href="https://cve.bz/cve/CVE-2026-61642"><img src="https://cve.bz/cve/badge/CVE-2026-61642.svg" alt="CVE-2026-61642"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
squid-cache squid>= 3.3.0.1, < 7.6

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12squidno fix listedDEBIAN-CVE-2026-61642
Debian13squid6.13-2+deb13u4DEBIAN-CVE-2026-61642
Debian14squid7.6-1DEBIAN-CVE-2026-61642
Ubuntu22.04:LTSsquid5.9-0ubuntu0.22.04.8UBUNTU-CVE-2026-61642 USN-8941-1
Ubuntu24.04:LTSsquid6.14-0ubuntu0.24.04.5UBUNTU-CVE-2026-61642 USN-8941-1
Ubuntu26.04:LTSsquid7.7-0ubuntu0.26.04.2UBUNTU-CVE-2026-61642 USN-8998-1
UbuntuPro:16.04:LTSsquid33.5.12-1ubuntu7.16+esm7UBUNTU-CVE-2026-61642 USN-8941-1
UbuntuPro:18.04:LTSsquid33.5.27-1ubuntu1.14+esm6UBUNTU-CVE-2026-61642 USN-8941-1
UbuntuPro:20.04:LTSsquid4.10-1ubuntu1.13+esm3UBUNTU-CVE-2026-61642 USN-8941-1
Red Hatenterprise_linux:8::appstreamlibecap, libecap-devel, libecap-debuginfo and 1 more0:1.0.1-2.module+el8.9.0+19703+a1da7223RHSA-2026:96078
Red Hatenterprise_linux:8::appstreamsquid, squid-debuginfo, squid-debugsource7:4.15-10.module+el8.10.0+25179+3c013c36.13RHSA-2026:96078
Red Hatenterprise_linux:9::appstreamsquid, squid-debuginfo, squid-debugsource7:5.5-27.el9_9.1RHSA-2026:98537
Red Hatenterprise_linux:10.3squid, squid-debuginfo, squid-debugsource7:6.10-15.el10_3.1RHSA-2026:98643
Red Hatenterprise_linux_eus:10.2squid, squid-debuginfo, squid-debugsource7:6.10-12.el10_2.2RHSA-2026:99123
Red Hatrhel_eus:9.8::appstreamsquid, squid-debuginfo, squid-debugsource7:5.5-26.el9_8.1RHSA-2026:99124
AlmaLinux8libecap, libecap-devel1.0.1-2.module_el8.6.0+2741+01592ae8ALSA-2026:96078
AlmaLinux8libecap, libecap-devel1.0.1-2.module_el8.6.0+3048+383bc947ALSA-2026:96078
AlmaLinux8squid7:4.15-10.module_el8.10.0+4354+d3ed158a.13ALSA-2026:96078
Rocky Linux8libecap0:1.0.1-2.module+el8.9.0+1437+df5ea8f0RLSA-2026:96078
Rocky Linux8squid7:4.15-10.module+el8.10.0+1758+80ba9f4bRLSA-2026:96078
Rocky Linux8squid7:4.15-10.module+el8.10.0+1881+7e31fb44.1RLSA-2026:96078
Rocky Linux8squid7:4.15-10.module+el8.10.0+1885+e30b7122.3RLSA-2026:96078
Rocky Linux8squid7:4.15-10.module+el8.10.0+1928+e8441768.5RLSA-2026:96078
Rocky Linux8squid7:4.15-10.module+el8.10.0+1985+eaf982f0.6RLSA-2026:96078
Rocky Linux8squid7:4.15-10.module+el8.10.0+2080+49064dbd.9RLSA-2026:96078
Rocky Linux8squid7:4.15-10.module+el8.10.0+40156+3f7c6af1.11RLSA-2026:96078
Rocky Linux8squid7:4.15-10.module+el8.10.0+40253+79b268c3.12RLSA-2026:96078
Rocky Linux9squid, squid-debuginfo, squid-debugsource7:5.5-27.el9_9.1RLSA-2026:98537
Rocky Linux10squid, squid-debuginfo, squid-debugsource7:6.10-15.el10_3.1RLSA-2026:98643
Azure Linux3squid6.13-6AZL-108531

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as having an Important severity because it allows network clients to bypass proxy security controls and poison shared web caches without requiring administrative privileges. In deployments where Squid acts as an intermediary or accelerator alongside HTTP caching layers, request desynchronization caused by specially crafted HTTP/1.1 Transfer-Encoding headers can lead to widespread cache contamination affecting other users. While exploitation requires client access to the proxy service, the resulting integrity impact across shared infrastructure justifies the Important rating.

Red Hat's mitigation

To mitigate this vulnerability, administrators should enforce rigorous server-side HTTP header validation by explicitly denying conflicting or ambiguous framing requests. In your squid.conf, this can be temporarily achieved by rejecting the problematic encoding outright using the directive request_header_access Transfer-Encoding deny all. Alternatively, administrators can neutralize the request smuggling attack vector entirely by disabling connection reuse with the settings client_persistent_connections off and server_persistent_connections off.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10squid-7:6.10-15.el10_3.1Fixed 2026-11-11RHSA-2026:98643
Red Hat Enterprise Linux 10.2 Extended Update Supportsquid-7:6.10-12.el10_2.2Fixed 2026-11-11RHSA-2026:99123
Red Hat Enterprise Linux 8squid:4-8100020261023120310.489197e6Fixed 2026-11-09RHSA-2026:96078
Red Hat Enterprise Linux 9squid-7:5.5-27.el9_9.1Fixed 2026-11-11RHSA-2026:98537
Red Hat Enterprise Linux 6squidAffected
Red Hat Enterprise Linux 6squid34Affected
Red Hat Enterprise Linux 7squidAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-61642.

Attack patterns (CAPEC)

  • CAPEC-33 HTTP Request Smuggling Likelihood: Medium · Severity: High
  • CAPEC-273 HTTP Response Smuggling Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON