CVE-2025-58056

A flaw in netty's parsing of chunk extensions in HTTP/1.1 messages with chunked encoding can lead to request smuggling issues with some reverse proxies.

Details

When encountering a newline character (LF) while parsing a chunk extension, netty interprets the newline as the end of the chunk-size line regardless of whether a preceding carriage return (CR) was found. This is in violation of the HTTP 1.1 standard which specifies that the chunk extension is terminated by a CRLF sequence (see the RFC).

This is by itself harmless, but consider an intermediary with a similar parsing flaw: while parsing a chunk extension, the intermediary interprets an LF without a preceding CR as simply part of the chunk extension (this is also in violation of the RFC, because whitespace characters are not allowed in chunk extensions). We can use this discrepancy to construct an HTTP request that the intermediary will interpret as one request but netty will interpret as two (all lines ending with CRLF, notice the LFs in the chunk extension):

POST /one HTTP/1.1
Host: localhost:8080
Transfer-Encoding: chunked

48;\nAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\n0

POST /two HTTP/1.1
Host: localhost:8080
Transfer-Encoding: chunked

0

The intermediary will interpret this as a single request. Once forwarded to netty, netty will interpret it as two separate requests. This is a problem, because attackers can then the intermediary, as well as perform standard request smuggling attacks against other live users (see this Portswigger article).

Disclosure

• This vulnerability was disclosed on June 18th, 2025 here: https://w4ke.info/2025/06/18/funky-chunks.html

Discussion

Discussion for this vulnerability can be found here:

• https://github.com/netty/netty/issues/15522
• https://github.com/JLLeitschuh/unCVEed/issues/1

Credit

• Credit to @JeppW for uncovering this vulnerability.
• Credit to @JLLeitschuh at Socket for coordinating the vulnerability disclosure.

This is a request smuggling issue which can be exploited for bypassing front-end access control rules as well as corrupting the responses served to other live clients.

The impact is high, but it only affects setups that use a front-end which:

1. Interprets LF characters (without preceding CR) in chunk extensions as part of the chunk extension.
2. Forwards chunk extensions without normalization.

Kodem intelligence

1. What is CVE-2025-58056? CVE-2025-58056 is a low-severity security vulnerability in io.netty:netty-codec-http (maven), affecting versions < 4.1.125.Final. It is fixed in 4.1.125.Final, 4.2.5.Final.
2. Which versions of io.netty:netty-codec-http are affected by CVE-2025-58056? io.netty:netty-codec-http (maven) versions < 4.1.125.Final is affected.
3. Is there a fix for CVE-2025-58056? Yes. CVE-2025-58056 is fixed in 4.1.125.Final, 4.2.5.Final. Upgrade to this version or later.
4. Is CVE-2025-58056 exploitable, and should I be worried? Whether CVE-2025-58056 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2025-58056 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2025-58056?
   • Upgrade io.netty:netty-codec-http to 4.1.125.Final or later
   • Upgrade io.netty:netty-codec-http to 4.2.5.Final or later