CVE-2026-42577

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 67% 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
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Netty is an asynchronous, event-driven network application framework. From 4.2.0.Final to 4.2.13.Final , Netty's epoll transport fails to detect and close TCP connections that receive a RST after being half-closed, leading to stale channels that are never cleaned up and, in some code paths, a 100% CPU busy-loop in the event loop thread. This vulnerability is fixed in 4.2.13.Final.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
32.9%
KEV
Not listed

Published

May 13, 2026

Last Modified

May 18, 2026

Advisory Details (3)

Auto-updated May 13, 2026
Patch available. Sources: github.
github Patch Available

Netty epoll transport denial of service via RST on half-closed TCP connection · Advisory · netty/netty · GitHub

https://github.com/netty/netty/security/advisories/GHSA-rwm7-x88c-3g2p
generic

Epoll: Correctly delete fd from epoll if there is nothing to handle by normanmaurer · Pull Request #16689 · netty/netty · GitHub

https://github.com/netty/netty/pull/16689
generic

Epoll: Correctly delete fd from epoll if there is nothing to handle (… · netty/netty@0ec3d97 · GitHub

https://github.com/netty/netty/commit/0ec3d97fab376e243d328ac95fbd288ba0f6e22d

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
io.netty:netty-transport-native-epoll4.2.0.Final ... 4.2.9.Final (13 versions)4.2.13.Final

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 50× 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 111 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-42577?
CVE-2026-42577 is a high vulnerability published on May 13, 2026. Netty is an asynchronous, event-driven network application framework. From 4.2.0.Final to 4.2.13.Final , Netty's epoll transport fails to detect and close TCP connections that receive a RST after being half-closed, leading to stale channels that are never cleaned up and, in some code paths, a 100%…
When was CVE-2026-42577 disclosed?
CVE-2026-42577 was first published in the National Vulnerability Database on May 13, 2026, with the most recent update on May 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-42577 actively exploited?
CVE-2026-42577 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 32.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-42577?
CVE-2026-42577 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-42577?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42577, 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-42577

Explore →

Is Your Infrastructure Affected by CVE-2026-42577?

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