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 78% 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.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 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)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
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(4)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2026-08-04redhat
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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
netty1:4.1.48-10 ... 1:4.1.48-9 (16 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
netty1:4.1.48-10 ... 1:4.1.48-9 (12 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
netty1:4.1.48-10 ... 1:4.1.48-16 (8 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
netty1:4.1.48-10 ... 1:4.1.48-16 (7 versions)——
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 14× in last 7d / 68× 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.

Showing the most recent 100 of 140 total refreshes for this CVE.

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

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 0% probability of exploitation in the next 30 days, which ranks it in the top 78.2% of all scored CVEs.
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