Security bypass via accepted identity transfer encoding
Published Oct 13, 2026 · Updated Oct 13, 2026
Request smuggling in Squid 3.3.0.1 through 7.5 allows attackers to bypass intermediary security via HTTP/1.1 headers. HttpHeader::parse in src/HttpHeader.cc accepts bare Transfer-Encoding identity and deletes that header instead of rejecting a coding without chunked framing. Exploitation requires a trusted client; a cache ahead of Squid also enables poisoning with arbitrary malicious content served to later clients.
Summary
What happened
Request smuggling in Squid 3.3.0.1 through 7.5 allows attackers to bypass intermediary security via HTTP/1.1 headers. HttpHeader::parse in src/HttpHeader.cc accepts bare Transfer-Encoding identity and deletes that header instead of rejecting a coding without chunked framing. Exploitation requires a trusted client; a cache ahead of Squid also enables poisoning with arbitrary malicious content served to later clients.
The record
- CVE
- CVE-2026-61642
- Published
- Oct 13, 2026
- Updated
- Oct 13, 2026
- Vendor
- The Squid Software Foundation
- Product
- Squid
- Classifications
- CWE-444, CWE-841, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 13, 2026CVE publishedPublication date reported by the CVE source.
- Oct 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 3.3.0.1, < 7.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started