Netty: Inbound data mixed with wrong outbound request

Summary

A bug in the Netty framework could cause incorrect data to be read from a response. This happens when a server sends multiple responses in a specific order. Affected versions of Netty are fixed in 4.2.13.Final and 4.1.133.Final, so update to these versions to resolve the issue.

What to do

No fix is available yet. Check with your software vendor for updates.

Affected software

Ecosystem	Vendor	Product	Affected versions
Debian:11	debian	netty	All versions
Debian:12	debian	netty	All versions
Debian:13	debian	netty	All versions
Debian:14	debian	netty	All versions

Original title

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() o...

Original 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.

osv CVSS3.1 7.3

https://security-tracker.debian.org/tracker/CVE-2026-42584 Vendor Advisory