Allocation of Resources Without Limits or Throttling The advisory has been revoked - it doesn't affect any version of package io.netty:netty-common  (opens in a new tab)


Threat Intelligence

Exploit Maturity
Proof of Concept
EPSS
0.73% (54th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-JAVA-IONETTY-20074866
  • published24 Sept 2026
  • disclosed10 Sept 2026
  • creditYazan Balawneh, Mike Read

Introduced: 10 Sep 2026

CVE-2026-93491  (opens in a new tab)
CWE-770  (opens in a new tab)

How to fix?

Upgrade io.netty:netty-common to version 4.1.138.Final, 4.2.18.Final or higher.

Amendment

This was deemed not a vulnerability.

Overview

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the enqueueMethod() method of HttpServerCodec, which packs the first 32 pipelined HTTP methods into a single long and then appends every further entry to the methodOverflowQueue ArrayDeque<Byte> with no size check. An attacker can exhaust the heap by pipelining a large number of minimal requests such as GET / HTTP/1.1\r\nHost: x\r\n\r\n on a single connection, with the growth coming from the codec's own per-connection bookkeeping rather than from buffered bodies. This requires the attacker to hold the connection open while withholding socket reads, so back pressure leaves responses unflushed and the decoder runs ahead of them, accumulating entries.