Resource Exhaustion Affecting strimzi-kafka-operator package, versions <0.51.0-r26


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.02% (5th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Resource Exhaustion vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CHAINGUARDLATEST-STRIMZIKAFKAOPERATOR-16786609
  • published21 May 2026
  • disclosed13 May 2026

Introduced: 13 May 2026

NewCVE-2026-42587  (opens in a new tab)
CWE-400  (opens in a new tab)

How to fix?

Upgrade Chainguard strimzi-kafka-operator to version 0.51.0-r26 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream strimzi-kafka-operator package and not the strimzi-kafka-operator package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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.