CVE-2026-42584
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.
How to fix
- netty netty4.1.133, 4.2.13 or later
- io.netty:netty-codec-http4.2.13.Final, 4.1.133.Final or later
- access.redhat.com/errata/RHSA-2026:49700
- access.redhat.com/errata/RHSA-2026:53644
- access.redhat.com/errata/RHSA-2026:53645
- access.redhat.com/errata/RHSA-2026:28010
- access.redhat.com/errata/RHSA-2026:53646
- access.redhat.com/errata/RHSA-2026:66545
- access.redhat.com/errata/RHSA-2026:66488
- access.redhat.com/errata/RHSA-2026:49701
- access.redhat.com/errata/RHSA-2026:42644
- access.redhat.com/errata/RHSA-2026:65126
- access.redhat.com/errata/RHSA-2026:25123
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| netty netty | v < 4.1.133, 4.2.0 ≤ v < 4.2.13 | 4.1.133, 4.2.13 |
| io.netty:netty-codec-httpMaven | 4.2.0.Alpha1 ≤ v < 4.2.13.Final, v < 4.1.133.Final | 4.2.13.Final, 4.1.133.Final |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.