NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

Netty: Memory Exhaustion in SctpMessageCompletionHandlerGHSA-2qj4-mmr9-4v2f

HIGHFix: netty/netty#17213

GHSA-2qj4-mmr9-4v2f is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in io.netty:netty-transport-sctp. A fix is available for io.netty:netty-transport-sctp — see the affected versions and patch details below.

Also known asCVE-2026-59902
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 15, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-2qj4-mmr9-4v2f.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk
0.00%0.39%0.78%1.17%0.4%0.7%0.4%0.4%Sep 26Nov 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
☕io.netty:netty-transport-sctp☕io.netty:netty-transport-sctp

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenio.netty:netty-transport-sctp≥ 4.2.0.Final&&< 4.2.17.Final4.2.17.Finalio.netty:netty-transport-sctp:4.2.17.Final
☕Mavenio.netty:netty-transport-sctpall versions4.1.137.Finalio.netty:netty-transport-sctp:4.1.137.Final

Affected Products

1 product · 2 configurations
Application
nettynetty
≥ 4.2.0 && < 4.2.17
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.netty:netty-transport-sctp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update io.netty:netty-transport-sctp to 4.2.17.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2qj4-mmr9-4v2f is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

An Important severity denial-of-service flaw was found in Netty's SCTP transport, which is shipped in a number of Red Hat offerings, including Red Hat build of Apache Camel for Spring Boot, JBoss EAP, Red Hat Single Sign-On, Red Hat JBoss Fuse, and Red Hat Enterprise Linux AI. The…

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. The upstream Netty project has published fixed releases, so updating to a Netty release that contains the upstream fix resolves the issue.
Source: Red Hat security advisory for GHSA-2qj4-mmr9-4v2f (CC BY 4.0)
ProductFixed inAdvisory
Red Hat build of Apache Camel 4.18.4 for Spring Boot 3.5.16netty-transport-sctpRHSA-2026:71675

Frequently Asked Questions

### 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 enf
O3 Security · Impact-Aware SCA

Is GHSA-2qj4-mmr9-4v2f in your dependencies?

Find it across Maven, including transitive dependencies.

Netty: Memory Exhaustion in SctpMessageCompletionHan…