Netty netty-codec-http2 HTTP2 Decompressor Resource Leak pre 4.1.135/4.2.15
CVE-2026-48043 Published on June 12, 2026

netty-codec-http2: ByteBuf Reference-Count Leak in DelegatingDecompressorFrameListener Leads to Memory Exhaustion
Netty is a network application framework for development of protocol servers and clients. In netty-codec-http2 prior to versions 4.1.135.Final and 4.2.15.Final, the `DelegatingDecompressorFrameListener` class orchestrates HTTP/2 decompression by embedding a per-stream `EmbeddedChannel` that runs the appropriate decompression codec (gzip, deflate, zstd) and forwards decompressed chunks to a wrapped listener. Each decompressed chunk is a pooled `ByteBuf` handed to an anonymous `ChannelInboundHandlerAdapter` tail handler, which becomes the sole owner responsible for releasing it. A remote peer could send frames that would result in the flow-controller throwing and so trigger a resource leak which at the end might take down the whole JVM due OOME. Versions 4.1.135.Final and 4.2.15.Final patch the issue.

NVD

Vulnerability Analysis

CVE-2026-48043 can be exploited with network access, and does not require authorization privileges or user interaction. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to have no impact on confidentiality and integrity, and a high impact on availability.

Attack Vector:
NETWORK
Attack Complexity:
LOW
Privileges Required:
NONE
User Interaction:
NONE
Scope:
UNCHANGED
Confidentiality Impact:
NONE
Integrity Impact:
NONE
Availability Impact:
HIGH

Weakness Types

What is a Resource Exhaustion Vulnerability?

The software does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources.

CVE-2026-48043 has been classified to as a Resource Exhaustion vulnerability or weakness.

What is a Memory Leak Vulnerability?

The software does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. This is often triggered by improper handling of malformed data or unexpectedly interrupted sessions. In some languages, developers are responsible for tracking memory allocation and releasing the memory. If there are no more pointers or references to the memory, then it can no longer be tracked and identified for release.

CVE-2026-48043 has been classified to as a Memory Leak vulnerability or weakness.

Missing Release of Resource after Effective Lifetime

The software does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed. When a resource is not released after use, it can allow attackers to cause a denial of service by causing the allocation of resources without triggering their release. Frequently-affected resources include memory, CPU, disk space, power or battery, etc.


Products Associated with CVE-2026-48043

You can be notified by email with stack.watch whenever vulnerabilities like CVE-2026-48043 are published in these products:

Netty
 
Red Hat Apache Camel Quarkus
 
Red Hat Quarkus
 
Red Hat Cryostat
 
Red Hat Serverless
 
Red Hat Amq Broker
 
Red Hat Apache Camel Hawtio
 
Red Hat Camel Quarkus
 
Red Hat Camel Spring Boot
 
Red Hat Apicurio Registry
 
Red Hat Debezium
 
Red Hat Build Keycloak
 
Red Hat Jboss Data Grid
 
Red Hat Enterprise Linux Ai
 
Red Hat Jboss Fuse
 
Red Hat Jboss Enterprise Application Platform
 
Red Hat Jbosseapxp
 
Red Hat Openshift Ai
 
Red Hat Openshift Devspaces
 
Red Hat Amq Streams
 
Red Hat Single Sign On
 
Red Hat Kafka
 
Red Hat Apache Camel Spring Boot
 

Affected Versions

netty: Red Hat Build of Apache Camel 3.33 for Quarkus 3.33.2.SP1: Red Hat OpenShift Dev Spaces 3.29: Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16: Red Hat build of Quarkus 3.27.4.SP1: Red Hat build of Quarkus 3.33.2.SP1: Red Hat Streams for Apache Kafka 2.9.4: Red Hat Cryostat 4: Red Hat OpenShift Serverless: Red Hat AMQ Broker 7: Red Hat build of Apache Camel - HawtIO 4: Red Hat build of Apache Camel 4 for Quarkus 3: Red Hat build of Apicurio Registry 3: Red Hat build of Debezium 3: Red Hat Build of Keycloak: Red Hat Data Grid 8: Red Hat Enterprise Linux AI (RHEL AI) 3: Red Hat Fuse 7: Red Hat JBoss Enterprise Application Platform 7: Red Hat JBoss Enterprise Application Platform Expansion Pack: Red Hat OpenShift AI (RHOAI): Red Hat OpenShift Dev Spaces: Red Hat streams for Apache Kafka 3: Red Hat Single Sign-On 7:

Exploit Probability

EPSS
0.61%
Percentile
44.45%

EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.