CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2026-42587 remediation guide

netty netty, netty-codec-http, netty-codec-http2

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 an...

Open CVE record
Productnetty netty, netty-codec-http, netty-codec-http2
Affected versions>= >= 4.2.0.Alpha1, < 4.2.13.Final, >= < 4.1.133.Final, < 4.1.133, >= 4.2.0 < 4.2.13
Fixed versions4.1.133, 4.2.13
Priority basisReview · CVSS 7.5 · EPSS 0.99%
01

Identify the affected asset

Confirm whether netty netty, netty-codec-http, netty-codec-http2 is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= >= 4.2.0.Alpha1, < 4.2.13.Final, >= < 4.1.133.Final, < 4.1.133, >= 4.2.0 < 4.2.13. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 4.1.133, 4.2.13. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.

CVE-2026-42587 Remediation Guide | SECUFOCUS NOW