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 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, 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
22%
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(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 10× in last 7d / 62× 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-26 20:39 UTCEG score recompute
  2. 2026-07-26 20:39 UTCVendor advisory
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-25 14:18 UTCEPSS rescore
  5. 2026-07-24 14:18 UTCEPSS rescore
  6. 2026-07-23 14:18 UTCEPSS rescore
  7. 2026-07-23 03:18 UTCEG score recompute
  8. 2026-07-22 14:08 UTCEPSS rescore
  9. 2026-07-21 15:25 UTCEPSS rescore
  10. 2026-07-20 17:08 UTCEPSS rescore
  11. 2026-07-19 14:31 UTCEPSS rescore
  12. 2026-07-19 14:31 UTCEPSS rescore
  13. 2026-07-19 02:29 UTCEPSS rescore
  14. 2026-07-18 10:04 UTCEPSS rescore
  15. 2026-07-16 23:17 UTCVendor advisory
  16. 2026-07-16 17:03 UTCEPSS rescore
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 16:57 UTCEPSS rescore
  19. 2026-07-15 16:19 UTCVendor advisory
  20. 2026-07-15 02:00 UTCEPSS rescore
  21. 2026-07-15 02:00 UTCEPSS rescore
  22. 2026-07-14 17:25 UTCVendor advisory
  23. 2026-07-13 22:31 UTCEPSS rescore
  24. 2026-07-13 18:58 UTCVendor advisory
  25. 2026-07-13 06:13 UTCEPSS rescore
Show 72 more
  1. 2026-07-13 06:13 UTCEPSS rescore
  2. 2026-07-12 17:48 UTCVendor advisory
  3. 2026-07-12 05:46 UTCEPSS rescore
  4. 2026-07-11 18:48 UTCVendor advisory
  5. 2026-07-11 08:27 UTCEPSS rescore
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-10 20:21 UTCVendor advisory
  8. 2026-07-09 21:55 UTCVendor advisory
  9. 2026-07-09 19:10 UTCEPSS rescore
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-08 22:04 UTCVendor advisory
  12. 2026-07-08 15:16 UTCEPSS rescore
  13. 2026-07-08 15:16 UTCEPSS rescore
  14. 2026-07-07 23:36 UTCVendor advisory
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-07 01:09 UTCVendor advisory
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-05 09:42 UTCVendor advisory
  21. 2026-07-05 02:30 UTCEPSS rescore
  22. 2026-07-04 10:56 UTCVendor advisory
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-03 09:49 UTCVendor advisory
  25. 2026-07-02 11:21 UTCVendor advisory
  26. 2026-07-01 15:07 UTCEPSS rescore
  27. 2026-07-01 12:34 UTCVendor advisory
  28. 2026-06-30 23:22 UTCEPSS rescore
  29. 2026-06-30 14:07 UTCVendor advisory
  30. 2026-06-29 15:32 UTCVendor advisory
  31. 2026-06-29 14:06 UTCEPSS rescore
  32. 2026-06-29 14:06 UTCEPSS rescore
  33. 2026-06-28 17:02 UTCVendor advisory
  34. 2026-06-28 14:07 UTCEPSS rescore
  35. 2026-06-28 04:56 UTCEPSS rescore
  36. 2026-06-28 04:56 UTCEPSS rescore
  37. 2026-06-27 18:35 UTCVendor advisory
  38. 2026-06-27 03:08 UTCEPSS rescore
  39. 2026-06-26 20:07 UTCVendor advisory
  40. 2026-06-25 21:41 UTCVendor advisory
  41. 2026-06-25 13:49 UTCEPSS rescore
  42. 2026-06-24 23:14 UTCVendor advisory
  43. 2026-06-24 14:05 UTCEPSS rescore
  44. 2026-06-24 00:46 UTCVendor advisory
  45. 2026-06-23 21:33 UTCEPSS rescore
  46. 2026-06-23 21:33 UTCEPSS rescore
  47. 2026-06-23 02:19 UTCVendor advisory
  48. 2026-06-22 14:25 UTCEPSS rescore
  49. 2026-06-22 14:25 UTCEPSS rescore
  50. 2026-06-22 03:52 UTCVendor advisory
  51. 2026-06-21 14:56 UTCEPSS rescore
  52. 2026-06-21 14:56 UTCEPSS rescore
  53. 2026-06-21 04:44 UTCVendor advisory
  54. 2026-06-21 01:59 UTCEPSS rescore
  55. 2026-06-21 01:59 UTCEPSS rescore
  56. 2026-06-20 06:09 UTCVendor advisory
  57. 2026-06-19 19:26 UTCEPSS rescore
  58. 2026-06-19 19:26 UTCEPSS rescore
  59. 2026-06-19 07:41 UTCVendor advisory
  60. 2026-06-18 17:52 UTCEPSS rescore
  61. 2026-06-18 17:52 UTCEPSS rescore
  62. 2026-06-17 17:53 UTCEPSS rescore
  63. 2026-06-16 17:53 UTCEPSS rescore
  64. 2026-06-15 17:49 UTCEPSS rescore
  65. 2026-06-15 17:49 UTCEPSS rescore
  66. 2026-06-15 13:37 UTCEG score recompute▼ 1.60
  67. 2026-06-15 03:24 UTCNVD updateCVSS v3 → 5.3
  68. 2026-06-14 23:18 UTCEPSS rescore
  69. 2026-06-13 23:00 UTCEPSS rescore
  70. 2026-06-12 23:12 UTCEPSS rescore
  71. 2026-06-12 18:13 UTCEG score recompute
  72. 2026-06-12 18:13 UTCNVD updatefirst tracked

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 77.6% 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