All vulnerabilities
CVE-2026-100666GHSA-2g6j-r8q9-5hr8

Netty 4.2.0 through 4.2.16 Response Desynchronization via HttpServerCodec

netty nettyFrameworks
CVSS
6.9Medium
ExploitationPublic exploit codeCISA's assessment says proof of concept code is public, assessed 30 Sep 2026. Not in the KEV catalogCISA via CVE List
Exploit odds (EPSS)0.24%Chance of exploitation activity in the next 30 days, higher than 14% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in4.2.17.FinalAlso 4.1.137.FinalCVE List
Published26 Sep 2026Updated 30 Sep 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

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.

Text from CVE List

Affected versions 4

  • nettyaffected: 4.2.0.Final before 4.2.17.FinalCVE List
  • nettyunaffected: 4.2.17.FinalCVE List
  • nettyaffected: all versions before 4.1.137.FinalCVE List
  • nettyunaffected: 4.1.137.FinalCVE List

References 2