Vulnerability 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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Netty | Netty | < 4.1.133 |
Related Weaknesses (CWE)
References
- https://github.com/netty/netty/security/advisories/GHSA-57rv-r2g8-2cj3ExploitVendor Advisory
- https://github.com/netty/netty/security/advisories/GHSA-57rv-r2g8-2cj3ExploitVendor Advisory
FAQ
What is CVE-2026-42584?
CVE-2026-42584 is a vulnerability with a CVSS score of 7.3 (HIGH). 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...
How severe is CVE-2026-42584?
CVE-2026-42584 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-42584?
Check the references section above for vendor advisories and patch information. Affected products include: Netty Netty.