No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Thu, 23 Jul 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 22 Jul 2026 16:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
Wed, 22 Jul 2026 05:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Netty
Netty netty |
|
| Vendors & Products |
Netty
Netty netty |
Tue, 21 Jul 2026 22:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Netty: HTTP/2 decompression leaks ByteBuf reference count when the decompressor channel is already closed (Direct memory leak / OOM DoS) | |
| Weaknesses | CWE-400 CWE-401 |
|
| References |
|
|
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-07-23T13:55:29.793Z
Reserved: 2026-06-23T14:55:09.116Z
Link: CVE-2026-56819
Updated: 2026-07-23T13:55:08.467Z
No data.
No data.
OpenCVE Enrichment
Updated: 2026-07-23T19:30:17Z