Security-control bypass via lenient chunked decoding
Published Nov 3, 2023 · Updated Feb 25, 2026
HTTP request smuggling in Squid 2.6 through 6.3 allows remote attackers to bypass frontend security via crafted chunked messages. The TeChunkedParser accepts 0x-prefixed chunk sizes and non-CRLF boundaries that peer servers can parse differently. Exploitation requires HTTP/1.1 or ICAP chunked encoding and an upstream server whose interpretation differs from Squid's.
Summary
What happened
HTTP request smuggling in Squid 2.6 through 6.3 allows remote attackers to bypass frontend security via crafted chunked messages. The TeChunkedParser accepts 0x-prefixed chunk sizes and non-CRLF boundaries that peer servers can parse differently. Exploitation requires HTTP/1.1 or ICAP chunked encoding and an upstream server whose interpretation differs from Squid's.
The record
- CVE
- CVE-2023-46846
- Published
- Nov 3, 2023
- Updated
- Feb 25, 2026
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 6
- Classifications
- CWE-444, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 3, 2023CVE publishedPublication date reported by the CVE source.
- Feb 25, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo