CVE-2026-45416

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9%, top 43% 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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, SslClientHelloHandler.decode() reads the 24-bit TLS handshake length and, when the ClientHello does not fit in the first record, eagerly allocates ctx.alloc().buffer(handshakeLength) (line 161). The guard at line 140 is handshakeLength > maxClientHelloLength && maxClientHelloLength != 0, and the commonly-used SniHandler/AbstractSniHandler constructors (SniHandler(Mapping), SniHandler(AsyncMapping), AbstractSniHandler()) pass maxClientHelloLength=0 and handshakeTimeoutMillis=0, so the length guard is disabled and no timeout is scheduled. A 16 MiB request exceeds the default pooled chunk size and becomes a huge/unpooled allocation performed immediately. The buffer is retained in the handler until the channel closes. Versions 4.1.135.Final and 4.2.15.Final patch the issue.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
EPSS PROB
1.6%
EPSS %ILE
74th
KEV
Not listed

Published

June 8, 2026

Last Modified

September 18, 2026

Advisory Details (3)

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

SNI handler pre-allocates up to 16 MiB from nine attacker bytes · Advisory · netty/netty · GitHub

https://github.com/netty/netty/security/advisories/GHSA-x4gw-5cx5-pgmh
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

Patch Availability(10)

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 rangeFix by version rangeDependents
netty1:4.1.48-10 ... 1:4.1.48-9 (16 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
netty1:4.1.48-10 ... 1:4.1.48-9 (12 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
netty1:4.1.48-10 ... 1:4.1.48-16 (8 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
netty1:4.1.48-10 ... 1:4.1.48-16 (7 versions)
  • every version on: no fix on record
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
io.netty:netty-handler4.0.0.Alpha1 ... 4.1.99.Final (228 versions)
  • 4.2.0.Final up to 4.2.15.Final: fixed in 4.2.15.Final
  • every version up to 4.1.135.Final: fixed in 4.1.135.Final
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 3× in last 7d / 43× 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 287 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-45416?
CVE-2026-45416 is a high 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, SslClientHelloHandler.decode() reads the 24-bit TLS handshake length and, when the ClientHello does not fit in the first record, eagerly allocates…
When was CVE-2026-45416 disclosed?
CVE-2026-45416 was first published on June 8, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45416 actively exploited?
CVE-2026-45416 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.6% probability of exploitation in the next 30 days (74th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45416?
CVE-2026-45416 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-45416?
A fix for CVE-2026-45416 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45416 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-45416?

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