HTTP Request Smuggling Affecting zipkin package, versions <3.6.1-r6
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-WOLFILATEST-ZIPKIN-16541962
- published9 May 2026
- disclosed13 May 2026
Introduced: 9 May 2026
NewCVE-2026-42584 (opens in a new tab)How to fix?
Upgrade Wolfi zipkin to version 3.6.1-r6 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream zipkin package and not the zipkin package as distributed by Wolfi.
See How to fix? for Wolfi 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.