Home

Description

Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, HttpClientCodec pairs each inbound response with an outbound request by queue.poll() once per response, including for 1xx. If the client pipelines GET then HEAD and the server sends 103, then 200 with GET body, then 200 for HEAD, the queue pairs HEAD with the first 200. The HEAD rule then skips reading that message’s body, so the GET entity bytes stay on the stream and the following 200 is parsed from the wrong offset. This vulnerability is fixed in 4.2.13.Final and 4.1.133.Final.

PUBLISHED Reserved 2026-04-28 | Published 2026-05-13 | Updated 2026-05-13 | Assigner GitHub_M




HIGH: 7.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Problem types

CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

Product status

>= 4.2.0.Alpha1, < 4.2.13.Final
affected

< 4.1.133.Final
affected

>= 4.2.0.Alpha1, < 4.2.13.Final
affected

< 4.1.133.Final
affected

References

github.com/.../netty/security/advisories/GHSA-57rv-r2g8-2cj3 exploit

github.com/.../netty/security/advisories/GHSA-57rv-r2g8-2cj3

cve.org (CVE-2026-42584)

nvd.nist.gov (CVE-2026-42584)

Download JSON