CRLF Injection Affecting netty-tcnative package, versions <2.0.77-150200.3.39.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.31% (23rd 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-SLES156-NETTYTCNATIVE-17278681
  • published10 Jun 2026
  • disclosed9 Jun 2026

Introduced: 9 Jun 2026

CVE-2026-41417  (opens in a new tab)
CWE-93  (opens in a new tab)
CWE-444  (opens in a new tab)

How to fix?

Upgrade SLES:15.6 netty-tcnative to version 2.0.77-150200.3.39.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream netty-tcnative package and not the netty-tcnative package as distributed by SLES. See How to fix? for SLES:15.6 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.

CVSS Base Scores

version 3.1