CVE-2026-47244

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

A fix is available — apply it.

Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, 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. Versions 4.1.135.Final and 4.2.15.Final patch the issue.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
21.0%
KEV
Not listed

Published

June 8, 2026

Last Modified

June 15, 2026

Advisory Details (3)

Auto-updated Jun 16, 2026
Patch available. Sources: github_release, github.
github Patch Available

HTTP/2: Advertised MAX_CONCURRENT_STREAMS not enforced · Advisory · netty/netty · GitHub

https://github.com/netty/netty/security/advisories/GHSA-5x3r-wrvg-rp6q
github_release Patch Available

netty-4.2.15.Final

Patch available: netty/netty netty-4.2.15.Final

https://github.com/netty/netty/releases/tag/netty-4.2.15.Final
github_release Patch Available

netty-4.1.135.Final

Patch available: netty/netty netty-4.1.135.Final

https://github.com/netty/netty/releases/tag/netty-4.1.135.Final

Vendor Advisories for CVE-2026-47244(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnetty-codec-http22026-06-17redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
io.netty:netty-codec-http24.1.0.Beta4 ... 4.1.99.Final (147 versions)4.1.135.Final—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 18× in last 7d / 77× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-05 22:16 UTCEG score recompute
  4. 2026-07-05 22:16 UTCVendor advisory
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 21:50 UTCEG score recompute
  7. 2026-07-04 21:50 UTCVendor advisory
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-03 20:59 UTCEG score recompute
  10. 2026-07-03 20:59 UTCVendor advisory
  11. 2026-07-02 20:29 UTCEG score recompute
  12. 2026-07-02 20:29 UTCVendor advisory
  13. 2026-07-01 20:04 UTCEG score recompute
  14. 2026-07-01 20:04 UTCVendor advisory
  15. 2026-07-01 15:07 UTCEPSS rescore
  16. 2026-06-30 23:22 UTCEPSS rescore
  17. 2026-06-30 19:40 UTCEG score recompute
  18. 2026-06-30 19:40 UTCVendor advisory
  19. 2026-06-29 19:16 UTCEG score recompute
  20. 2026-06-29 19:16 UTCVendor advisory
  21. 2026-06-29 14:06 UTCEPSS rescore
  22. 2026-06-29 14:06 UTCEPSS rescore
  23. 2026-06-28 17:56 UTCEG score recompute
  24. 2026-06-28 17:56 UTCVendor advisory
  25. 2026-06-28 14:07 UTCEPSS rescore
Show 52 more
  1. 2026-06-28 04:56 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-27 17:31 UTCEG score recompute
  4. 2026-06-27 17:31 UTCVendor advisory
  5. 2026-06-27 03:08 UTCEPSS rescore
  6. 2026-06-26 17:06 UTCEG score recompute
  7. 2026-06-26 17:06 UTCVendor advisory
  8. 2026-06-25 16:41 UTCEG score recompute
  9. 2026-06-25 16:41 UTCVendor advisory
  10. 2026-06-25 13:49 UTCEPSS rescore
  11. 2026-06-24 16:16 UTCEG score recompute
  12. 2026-06-24 16:16 UTCVendor advisory
  13. 2026-06-24 14:05 UTCEPSS rescore
  14. 2026-06-23 21:33 UTCEPSS rescore
  15. 2026-06-23 21:33 UTCEPSS rescore
  16. 2026-06-23 15:51 UTCEG score recompute
  17. 2026-06-23 15:51 UTCVendor advisory
  18. 2026-06-22 14:25 UTCEPSS rescore
  19. 2026-06-22 14:25 UTCEPSS rescore
  20. 2026-06-22 13:48 UTCEG score recompute
  21. 2026-06-22 13:48 UTCVendor advisory
  22. 2026-06-21 14:56 UTCEPSS rescore
  23. 2026-06-21 14:56 UTCEPSS rescore
  24. 2026-06-21 10:55 UTCEG score recompute
  25. 2026-06-21 10:55 UTCVendor advisory
  26. 2026-06-21 01:59 UTCEPSS rescore
  27. 2026-06-21 01:59 UTCEPSS rescore
  28. 2026-06-20 07:53 UTCEG score recompute
  29. 2026-06-20 07:53 UTCVendor advisory
  30. 2026-06-19 19:26 UTCEPSS rescore
  31. 2026-06-19 19:26 UTCEPSS rescore
  32. 2026-06-19 03:28 UTCEG score recompute
  33. 2026-06-19 03:28 UTCVendor advisory
  34. 2026-06-18 17:52 UTCEPSS rescore
  35. 2026-06-18 17:52 UTCEPSS rescore
  36. 2026-06-18 02:49 UTCEG score recompute
  37. 2026-06-17 17:53 UTCEPSS rescore
  38. 2026-06-17 02:24 UTCEG score recompute
  39. 2026-06-16 17:53 UTCEPSS rescore
  40. 2026-06-16 01:59 UTCEG score recompute
  41. 2026-06-15 17:49 UTCEPSS rescore
  42. 2026-06-15 17:49 UTCEPSS rescore
  43. 2026-06-15 01:35 UTCEG score recompute
  44. 2026-06-14 23:18 UTCEPSS rescore
  45. 2026-06-14 01:10 UTCEG score recompute
  46. 2026-06-13 23:00 UTCEPSS rescore
  47. 2026-06-13 00:46 UTCEG score recompute
  48. 2026-06-12 23:12 UTCEPSS rescore
  49. 2026-06-12 00:21 UTCEG score recompute
  50. 2026-06-10 23:56 UTCEG score recompute
  51. 2026-06-09 23:32 UTCEG score recompute
  52. 2026-06-08 23:08 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-47244?
CVE-2026-47244 is a medium vulnerability published on June 8, 2026. Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, DefaultHttp2Connection.DefaultEndpoint initialises maxActiveStreams/maxStreams to Integer.MAXVALUE, and Http2Settings never inserts…
When was CVE-2026-47244 disclosed?
CVE-2026-47244 was first published in the National Vulnerability Database on June 8, 2026, with the most recent update on June 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47244 actively exploited?
CVE-2026-47244 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47244?
CVE-2026-47244 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-47244?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47244, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47244

Explore →

Is Your Infrastructure Affected by CVE-2026-47244?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs