Allocation of Resources Without Limits or Throttling Affecting io.netty:netty-codec-http3 package, versions [4.2.0.Final,4.2.18.Final)


Severity

Recommended
0.0
high
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

Exploit Maturity
Proof of Concept
EPSS
0.34% (26th 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-20154840
  • published27 Sept 2026
  • disclosed26 Sept 2026
  • creditmanus-use

Introduced: 26 Sep 2026

NewCVE-2026-100661  (opens in a new tab)
CWE-770  (opens in a new tab)

How to fix?

Upgrade io.netty:netty-codec-http3 to version 4.2.18.Final or higher.

Overview

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in QpackUtil.decodePrefixedInteger, which places no bound on continuation bytes, unlike the HPACK decoder that stops at shift == 56, so an unterminated run returns -1 for buffer exhaustion and the caller returns without consuming anything. An attacker can grow the per-connection cumulator without bound to reach OutOfMemoryError, and consume event-loop CPU quadratically as every subsequent decode attempt rescans the whole buffer, by opening a client-initiated unidirectional QUIC stream and sending stream type 0x03 followed by a trigger byte such as 0xFF and an indefinite run of 0x80 continuation bytes. This requires only an established HTTP/3 connection and a client-initiated unidirectional stream, and either QPACK unidirectional stream reaches the decoder.

CVSS Base Scores

version 4.0
version 3.1