CVE-2026-100666
Received
Received - Intake
HTTP/1.1 Response Splitting in Netty HttpServerCodec
Vulnerability report for CVE-2026-100666, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.
Publication date: 2026-09-26
Last updated on: 2026-09-26
Assigner: VulnCheck
Description
Description
Netty's HttpServerCodec (io.netty:netty-codec-http) in versions 4.2.0.Final through 4.2.16.Final and in versions up to and including 4.1.136.Final pairs each outbound response with an inbound request by calling pollMethod() once per response, including for 1xx informational responses. If a client pipelines an HTTP/1.1 GET carrying an Expect: 100-continue header followed by a HEAD request, the 100 Continue response consumes the queued GET method, so the subsequent 200 OK for the GET is paired with HEAD and its body is dropped, while the following 200 OK for the HEAD request is written with a body. This desynchronizes HTTP parsing on the connection: the GET entity is never delivered and the HEAD response body is interpreted as the GET body, resulting in response splitting and unsafe connection reuse. Fixed in 4.2.17.Final and 4.1.137.Final.
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| netty | netty_codec_http | From 4.2.0_Final (inc) to 4.2.16_Final (inc) |
| netty | netty_codec_http | to 4.1.136_Final (inc) |
| netty | netty_codec_http | 4.2.17_Final |
| netty | netty_codec_http | 4.1.137_Final |
| netty | netty | From 4.2.0 (inc) to 4.2.16 (inc) |
| netty | netty | to 4.1.136 (inc) |
| netty | netty | 4.2.17 |
| netty | netty | 4.1.137 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-444 | The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination. |