HTTP Request Smuggling Affecting strimzi-kafka-operator-kafka-thirdparty-libs-cc package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.04% (12th 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 IDSNYK-MINIMOSLATEST-STRIMZIKAFKAOPERATORKAFKATHIRDPARTYLIBSCC-16707783
  • published16 May 2026
  • disclosed13 May 2026

Introduced: 13 May 2026

NewCVE-2026-42584  (opens in a new tab)
CWE-444  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest strimzi-kafka-operator-kafka-thirdparty-libs-cc.

NVD Description

Note: Versions mentioned in the description apply only to the upstream strimzi-kafka-operator-kafka-thirdparty-libs-cc package and not the strimzi-kafka-operator-kafka-thirdparty-libs-cc 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, HttpClientCodec pairs each inbound response with an outbound request by queue.poll() once per response, including for 1xx. If the client pipelines GET then HEAD and the server sends 103, then 200 with GET body, then 200 for HEAD, the queue pairs HEAD with the first 200. The HEAD rule then skips reading that message’s body, so the GET entity bytes stay on the stream and the following 200 is parsed from the wrong offset. This vulnerability is fixed in 4.2.13.Final and 4.1.133.Final.