CVE-2026-42587

Netty: HttpContentDecompressor maxAllocation bypass via Content-Encoding: br/zstd/snappy enables decompression bomb DoS

Published May 13, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, HttpContentDecompressor accepts a maxAllocation parameter to limit decompression buffer size and prevent decompression bomb attacks. This limit is correctly enforced for gzip and deflate encodings via ZlibDecoder, but is silently ignored when the content encoding is br (Brotli), zstd, or snappy. An attacker can bypass the configured decompression limit by sending a compressed payload with Content-Encoding: br instead of Content-Encoding: gzip, causing unbounded memory allocation and out-of-memory denial of service. The same vulnerability exists in DelegatingDecompressorFrameListener for HTTP/2 connections. This vulnerability is fixed in 4.2.13.Final and 4.1.133.Final.

Analysis

AI-generated

Technical impact

A failure to enforce the maxAllocation parameter in Netty’s HttpContentDecompressor allows an attacker to supply a deeply compressed payload that bypasses the memory limit when the Content‑Encoding header is set to brotli, zstd, or snappy. The decompressor then allocates an unbounded amount of memory, potentially exhausting system resources and causing an out‑of‑memory denial of service. This weakness is identified as CWE‑400 and CWE‑770, the former being a generic resource‑exhaustion flaw and the latter indicating an insufficient system capability to handle the resource demands.

Affected Systems

The vulnerability affects Netty components io.netty:netty-codec-http, io.netty:netty-codec-http2, and the core netty library. All releases before 4.2.13.Final and 4.1.133.Final are susceptible, including earlier 4.x and 4.1.x versions. HTTP/2 connections through DelegatingDecompressorFrameListener are also impacted.

Risk and Exploitability

The CVSS score of 7.5 indicates substantial severity. The EPSS score of 0.00018 (≈0.018 %) indicates a very low but non‑zero probability of exploitation, consistent with the fact that the flaw requires a specially crafted HTTP request. The vulnerability is not listed in CISA’s KEV catalog, yet it can be triggered wherever Netty is used to decode compressed HTTP traffic. The likely attack vector is an HTTP request containing a maliciously compressed payload with a Content‑Encoding header set to br, zstd, or snappy, causing the server to allocate memory beyond the configured limit.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Netty resources to version 4.2.13.Final or later, or 4.1.133.Final or later.
  • If an upgrade is not immediately possible, configure the Netty pipeline to reject or drop requests that use Content‑Encoding headers of brotli, zstd, or snappy.
  • Continuously monitor memory usage of Netty processes and configure automatic restarts or OOM detection mechanisms to mitigate prolonged resource exhaustion.

Generated by OpenCVE AI on May 29, 2026 at 02:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-f6hv-jmp6-3vwv Netty: HttpContentDecompressor maxAllocation bypass when Content-Encoding set to br/zstd/snappy leads to decompression bomb DoS
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
CPEs cpe:2.3:a:netty:netty:*:*:*:*:*:*:*:*
Type Values Removed Values Added
First Time appeared Io.netty
Io.netty netty-codec-http
Io.netty netty-codec-http2
Netty
Netty netty
Vendors & Products Io.netty
Io.netty netty-codec-http
Io.netty netty-codec-http2
Netty
Netty netty
Type Values Removed Values Added
Description Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, HttpContentDecompressor accepts a maxAllocation parameter to limit decompression buffer size and prevent decompression bomb attacks. This limit is correctly enforced for gzip and deflate encodings via ZlibDecoder, but is silently ignored when the content encoding is br (Brotli), zstd, or snappy. An attacker can bypass the configured decompression limit by sending a compressed payload with Content-Encoding: br instead of Content-Encoding: gzip, causing unbounded memory allocation and out-of-memory denial of service. The same vulnerability exists in DelegatingDecompressorFrameListener for HTTP/2 connections. This vulnerability is fixed in 4.2.13.Final and 4.1.133.Final.
Title Netty: HttpContentDecompressor maxAllocation bypass via Content-Encoding: br/zstd/snappy enables decompression bomb DoS
Weaknesses CWE-400
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Sep 18, 2026, 12:04 PM
Reserved
Apr 28, 2026, 5:26 PM
Status
Modified
Published
May 13, 2026, 7:17 PM
Modified
Oct 26, 2026, 5:10 PM
Severity
Important
Public date
May 13, 2026, 6:22 PM