CVE details
CVE-2026-42581
Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, HttpObjectDecoder strips a conflicting Content-Length header when a request carries both Transfer-Encoding: chunked and Content-Length, but only for HTTP/1.1 messages. The guard is absent for HTTP/1.0. An attacker that sends an HTTP/1.0 request with both headers causes Netty to decode the body as chunked while leaving Content-Length intact in the forwarded HttpMessage. Any downstream proxy or handler that trusts Content-Length over Transfer-Encoding will disagree on message boundaries, enabling request smuggling. This vulnerability is fixed in 4.2.13.Final and 4.1.133.Final.
Affected ports (1)
| Port | Package | Version | Status | Maintainer |
|---|---|---|---|---|
| java/netty | netty | 4.1.53_2 | unaddressed | glewis@FreeBSD.org |
Template for a VuXML entry
Range taken from the CVE record, check it before committing. make newentry in security/vuxml creates the vid.
<vuln vid="FIXME (make newentry)">
<topic>FIXME -- FIXME</topic>
<affects>
<package>
<name>netty</name>
<range><lt>4.1.133</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Netty is an asynchronous, event-driven network application framework.
Prior to 4.2.13.Final and 4.1.133.Final, HttpObjectDecoder strips a
conflicting Content-Length header when a request carries both
Transfer-Encoding: chunked and Content-Length, but only for HTTP/1.1
messages. The guard is absent for HTTP/1.0. An attacker that sends an
HTTP/1.0 request with both headers causes Netty to decode the body as
chunked while leaving Content-Length intact in the forwarded
HttpMessage. Any downstream proxy or handler that trusts
Content-Length over Transfer-Encoding will disagree on message
boundaries, enabling request smuggling. This vulnerability is fixed in
4.2.13.Final and 4.1.133.Final.</p>
</body>
</description>
<references>
<cvename>CVE-2026-42581</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2026-42581</url>
</references>
<dates>
<discovery>2026-05-13</discovery>
<entry>2026-10-25</entry>
</dates>
</vuln>