CVE-2026-50560

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 77% 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, nvd
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, Netty HTTP/2 max header size handling produces an attack similar to HTTP/2 Rapid Reset. There is a setting in the http2 specification called SETTINGS_MAX_HEADER_LIST_SIZE. When a client sends that setting to Netty, it appears that Netty will behave as follows: read the request; proxy the request to the origin; attempt to produce a response; and create an exception while writing the headers for the response. Functionally, this should be similar to the http2 reset attack, but with a different on-the-wire signature. Versions 4.1.135.Final and 4.2.15.Final patch the issue.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/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%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

June 12, 2026

Last Modified

June 15, 2026

Advisory Details (4)

Auto-updated Jun 12, 2026
Patch available. Sources: github_release, github.
generic

RFC 9113: HTTP/2

https://www.rfc-editor.org/rfc/rfc9113.html#name-defined-settings
github Patch Available

Netty susceptible to HTTP/2 Reset Attack with different on-the-wire signature · Advisory · netty/netty · GitHub

https://github.com/netty/netty/security/advisories/GHSA-563q-j3cm-6jxm
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-50560(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 6× in last 7d / 33× 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 190 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-50560?
CVE-2026-50560 is a medium vulnerability published on June 12, 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, Netty HTTP/2 max header size handling produces an attack similar to HTTP/2 Rapid Reset. There is a setting in the http2 specification called…
When was CVE-2026-50560 disclosed?
CVE-2026-50560 was first published in the National Vulnerability Database on June 12, 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-50560 actively exploited?
CVE-2026-50560 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 76.9% of all scored CVEs.
What is the CVSS score of CVE-2026-50560?
CVE-2026-50560 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-50560?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50560, 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-50560

Explore →

Is Your Infrastructure Affected by CVE-2026-50560?

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

Start Free Scan →Browse All CVEs