Vulnerability 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 Score
HIGH
Related Weaknesses (CWE)
References
- https://github.com/netty/netty/security/advisories/GHSA-2g6j-r8q9-5hr8
- https://www.vulncheck.com/advisories/netty-4.2.0-through-4.2.17-response-desynch
- https://github.com/netty/netty/security/advisories/GHSA-2g6j-r8q9-5hr8
FAQ
What is CVE-2026-100666?
CVE-2026-100666 is a vulnerability with a CVSS score of 7.3 (HIGH). 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 ...
How severe is CVE-2026-100666?
CVE-2026-100666 has been rated HIGH with a CVSS base score of 7.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-100666?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.