PT-2026-47612 · Netty · Netty
Published
2026-06-08
·
Updated
2026-06-12
·
CVE-2026-47244
CVSS v3.1
5.3
Medium
| Vector | AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
Name of the Vulnerable Software and Affected Versions
Netty versions prior to 4.1.135.Final
Netty versions prior to 4.2.15.Final
Description
In the network application framework,
DefaultHttp2Connection.DefaultEndpoint initializes maxActiveStreams and maxStreams to Integer.MAX VALUE, while Http2Settings does not insert SETTINGS MAX CONCURRENT STREAMS by default. If the application does not explicitly call initialSettings().maxConcurrentStreams(n), the HTTP/2 server advertises and enforces no limit on concurrent streams. This allows a single TCP connection to create hundreds of thousands of long-lived stream objects, as each open stream allocates a DefaultStream object, PropertyMap slots, flow-controller state, and an IntObjectHashMap entry. This condition also enables Rapid-Reset amplification, where the lack of a low concurrent cap increases the workload on the backend.Recommendations
Update to version 4.1.135.Final.
Update to version 4.2.15.Final.
As a temporary mitigation, explicitly call
initialSettings().maxConcurrentStreams(n) to define a limit for concurrent streams.Fix
Resource Exhaustion
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
Netty