CVE-2026-56819 PUBLISHED

Netty: HTTP/2 decompression leaks ByteBuf reference count when the decompressor channel is already closed (Direct memory leak / OOM DoS)

Assigner: GitHub_M
Reserved: 23.06.2026 Published: 21.07.2026 Updated: 22.07.2026

Netty is a network application framework for development of protocol servers and clients. In versions 4.2.0.Final through 4.2.15.Final and 4.1.0.Final through 4.1.135.Final, a remote unauthenticated peer can leak one direct ByteBuf per HTTP/2 DATA frame in applications that enable HTTP/2 content decompression via DelegatingDecompressorFrameListener. When a DATA frame is processed for a stream whose decompressor has already been closed, Http2Decompressor.decompress(...) calls decompressor.writeInbound(data.retain()) and does not release the retained buffer on the error path, eventually exhausting direct memory and crashing the JVM. This issue is fixed in versions 4.1.136.Final and 4.2.16.Final.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS Score: 7.5

Product Status

Vendor netty
Product netty
Versions
  • Version >= 4.2.0.Final, < 4.2.16.Final is affected
  • Version >= 4.1.0.Final, < 4.1.136.Final is affected

References

Problem Types

  • CWE-400: Uncontrolled Resource Consumption CWE
  • CWE-401: Missing Release of Memory after Effective Lifetime CWE