CRLF Injection Affecting netty package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.25% (17th 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-ECHOLATEST-NETTY-18426993
  • published30 Jul 2026
  • disclosed29 Jul 2026

Introduced: 29 Jul 2026

NewCVE-2026-59920  (opens in a new tab)
CWE-93  (opens in a new tab)

How to fix?

There is no fixed version for Echo:latest netty.

NVD Description

Note: Versions mentioned in the description apply only to the upstream netty package and not the netty package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

Netty is an asynchronous, event-driven network application framework. In versions prior to 4.1.136.Final and 4.2.16.Final, Netty's STOMP encoder ( StompSubframeEncoder ) does not escape or validate header values in  CONNECT  and  CONNECTED  frames, so raw newline ( \n ) characters in a header value are written directly to the wire, allowing an attacker who controls a header value to inject additional STOMP headers. This happens because the encoder intentionally skips escaping for CONNECT/CONNECTED frames per the STOMP 1.2 specification but never rejects the raw newlines, and since a broker parses each line as a separate header, an attacker controlling a value such as a user-supplied login or passcode can overwrite connection parameters or add authentication/role headers to bypass authentication or escalate privileges (the actual impact is broker-dependent). The issue is fixed in versions 4.1.136.Final and 4.2.16.Final.

CVSS Base Scores

version 3.1