GHSA-2qj4-mmr9-4v2f Netty: Memory Exhaustion in SctpMessageCompletionHandler

• Maven io.netty:netty-transport-sctp: >= 4.2.0.Final, < 4.2.17.Final → fixed in 4.2.17.Final • Maven io.netty:netty-transport-sctp: < 4.1.137.Final → fixed in 4.1.137.Final

Summary SctpMessageCompletionHandler does not limit the total size of buffered fragments, allowing an unauthenticated attacker to cause an OutOfMemoryError by sending large SCTP fragments. Details `io.netty.handler.codec.sctp.SctpMessageCompletionHandler` buffers fragments for incomplete SCTP messages. The fix for CVE-2026-46340 fixed unbounded memory growth by introducing limits on the number of concurrent incomplete messages (maxIncompleteSctpMessages) and the number of fragments per message (maxFragments). While the count of fragments is now bounded, the handler still does not enforce a maximum size in bytes. With the default limits of 128 messages and 128 fragments, and a typical max SCTP chunk size of 64KB, an attacker can consume up to ~1GB per connection. By opening a small number of concurrent connections, an attacker can easily exhaust the server's memory, causing an OutOfMemoryError. Impact Memory Exhaustion. Any application using Netty's SCTP transport with SctpMessageCompletionHandler is impacted.