Medium

Netty HTTP/2: Advertised MAX_CONCURRENT_STREAMS are not enforced

  • Disclosed: 08.06.2026
  • Updated: 11.10.2026 13:20

Impact

DefaultHttp2Connection.DefaultEndpoint initialises maxActiveStreams/maxStreams to Integer.MAX_VALUE, and Http2Settings never inserts SETTINGS_MAX_CONCURRENT_STREAMS by default (Http2Settings.java:305-307 only clamps a user-supplied value). Unless the application explicitly calls initialSettings().maxConcurrentStreams(n), a Netty HTTP/2 server advertises no limit and enforces none locally. Each open stream allocates a DefaultStream object, PropertyMap slots, flow-controller state and IntObjectHashMap entry; with ~2^30 permissible odd stream IDs a single TCP connection can create hundreds of thousands of long-lived stream objects. This is also the precondition for CVE-2023-44487-style Rapid-Reset amplification, where the absence of a low concurrent cap multiplies backend work.

Resources

https://www.rfc-editor.org/rfc/rfc7540.html#section-6.5.2

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Java / Kotlin (Maven) io.netty:netty-codec-http2 >= 4.2.0.Final, < 4.2.15.Final, < 4.1.135.Final 4.2.15.Final, 4.1.135.Final

References

CVSS score 5.3/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Weakness (CWE)
CWE-400
Platform
Java / Kotlin (Maven)
Package
io.netty:netty-codec-http2
Disclosed
08.06.2026
Updated
11.10.2026 13:20

Sources and licenses

OSV / GitHub Advisory Database - GHSA-5x3r-wrvg-rp6q - CC BY 4.0

Vulnerability history: io.netty:netty-codec-http2

All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (11) in the archive
Total entries
11
First → latest
03.2021 07.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • High 5
  • Medium 6

Disclosures per year

  1. 2021: 2
  2. 2022: 0
  3. 2023: 1
  4. 2024: 0
  5. 2025: 1
  6. 2026: 7
Severity:
  1. High · 7.5 CVE-2026-56819 >= 4.2.0, < 4.2.16.Final, >= 4.1.0.Final, < 4.1.136.Final 4.2.16.Final, 4.1.136.Final
  2. Netty HTTP/2: Advertised MAX_CONCURRENT_STREAMS are not enforced this entry
    Medium · 5.3 CVE-2026-47244 >= 4.2.0.Final, < 4.2.15.Final, < 4.1.135.Final 4.2.15.Final, 4.1.135.Final
  3. High · 7.5 CVE-2026-42587 >= 4.2.0.Alpha1, < 4.2.13.Final, < 4.1.133.Final 4.2.13.Final, 4.1.133.Final
  4. High CVE-2026-33871 < 4.1.132.Final, >= 4.2.0.Alpha1, < 4.2.11.Final 4.1.132.Final, 4.2.11.Final
  5. High · 7.5 CVE-2025-55163 >= 4.2.0.Alpha1, < 4.2.4.Final, < 4.1.124.Final 4.2.4.Final, 4.1.124.Final
  6. High · 7.5 ghsa-xpw8-rcwv-8f8p < 4.1.100.Final 4.1.100.Final

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.