CRLF Injection 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-16541966
- published9 May 2026
- disclosed6 May 2026
Introduced: 6 May 2026
NewCVE-2026-41417 (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 allows request-line validation to be bypassed when a DefaultHttpRequest or DefaultFullHttpRequest is created first and its URI is later changed via setUri(). The constructors reject CRLF and whitespace characters that would break the start-line, but setUri() does not apply the same validation. HttpRequestEncoder and RtspEncoder then write the URI into the request line verbatim. If attacker-controlled input reaches setUri(), this enables CRLF injection and insertion of additional HTTP or RTSP requests, leading to HTTP request smuggling or desynchronization on the HTTP side and request injection on the RTSP side. This issue is fixed in versions 4.2.13.Final and 4.1.133.Final.