Memory Leak Affecting netty package, versions <4.1.136-150200.4.53.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.47% (39th 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-SLES157-NETTY-18533036
  • published5 Aug 2026
  • disclosed4 Aug 2026

Introduced: 4 Aug 2026

CVE-2026-56818  (opens in a new tab)
CWE-401  (opens in a new tab)
CWE-703  (opens in a new tab)

How to fix?

Upgrade SLES:15.7 netty to version 4.1.136-150200.4.53.1 or higher.

NVD Description

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

Netty is an asynchronous, event-driven network application framework. Prior to 4.1.136.Final and 4.2.16.Final, the RedisArrayAggregator Redis codec clears retained partial aggregate state when the maxNestedArrayDepth limit is exceeded, but it does not clear the same state when the sibling maxElements limit is exceeded. A peer can start a valid RESP array, send a bulk string child, then send a nested array header longer than the configured maxElements. Netty throws a decoder exception in decodeRedisArrayHeader, but the existing partial aggregate remains retained in the handler. If the application leaves the channel alive after the exception, later messages are still consumed into the pre-error aggregate, allowing an unauthenticated peer to keep attacker-controlled aggregate state alive across a security-limit exception and pin retained pooled buffers. This issue is fixed in versions 4.1.136.Final and 4.2.16.Final.

CVSS Base Scores

version 3.1