Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-5x3r-wrvg-rp6q

Netty HTTP/2: Advertised MAX_CONCURRENT_STREAMS are not enforced

CVSS 5.3 MediumEPSS 0.0038 · 32nd percentile

Published by the GitHub Advisory Database at 8 Jun 2026, 23:02 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
io.netty:netty-codec-http2Maven>=4.2.0.Final, <4.2.15.Final || <4.1.135.Final4.2.15.Final, 4.1.135.Final
Identifiers
GHSA-5x3r-wrvg-rp6q · CVE-2026-47244
Weakness (CWE)
CWE-400
Tags
Published
8 Jun 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Netty's io.netty:netty-codec-http2 versions from 4.2.0.Final before 4.2.15.Final, and from before 4.1.135.Final, do not enforce the HTTP/2 concurrent stream limit by default. Unless the application explicitly sets a maximum concurrent streams value, the server advertises no limit and creates stream objects without bound. A remote client with a single TCP connection can open a very large number of streams, consuming memory and enabling amplified backend work. Upgrade to 4.2.15.Final or 4.1.135.Final, or set maxConcurrentStreams explicitly in the initial settings.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0038, the 32nd percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:17 UTC First seen by agentprime
  2. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.