Resource Exhaustion Affecting strimzi-kafka-operator-0.45-kafka-base package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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 IDSNYK-MINIMOSLATEST-STRIMZIKAFKAOPERATOR045KAFKABASE-16542395
- published9 May 2026
- disclosed13 May 2026
Introduced: 9 May 2026
NewCVE-2026-42587 (opens in a new tab)How to fix?
There is no fixed version for Minimos:latest strimzi-kafka-operator-0.45-kafka-base.
NVD Description
Note: Versions mentioned in the description apply only to the upstream strimzi-kafka-operator-0.45-kafka-base package and not the strimzi-kafka-operator-0.45-kafka-base package as distributed by Minimos.
See How to fix? for Minimos:latest 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.