Skip to main content
← All vulnerabilities
CVE-2026-42587GHSA-F6HV-JMP6-3VWV

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

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 4.2.13.Final, 4.1.133.Final
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: poc
  • Automatable: yes
  • Technical impact: partial

Summary

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.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: poc · Automatable: yes · Technical impact: partial

  3. Record last updated

Affected versions

  • netty netty

    From 4.2.0.Alpha1 · fixed in 4.2.13.Final; fixed in 4.1.133.Final

  • io.netty netty-codec-http

    From 4.2.0.Alpha1 · fixed in 4.2.13.Final; fixed in 4.1.133.Final

  • io.netty netty-codec-http2

    From 4.2.0.Alpha1 · fixed in 4.2.13.Final; fixed in 4.1.133.Final

  • io.netty:netty-codec-httpMaven

    From 4.2.0.Alpha1 · fixed in 4.2.13.Final

  • io.netty:netty-codec-http2Maven

    From 4.2.0.Alpha1 · fixed in 4.2.13.Final

  • io.netty:netty-codec-httpMaven

    fixed in 4.1.133.Final

  • io.netty:netty-codec-http2Maven

    fixed in 4.1.133.Final

References 1

GitHub · netty/netty