CVE-2026-50010

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% 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: cna:github_m, epss
Trending — Patch released this week
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

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, SimpleTrustManagerFactory.engineGetTrustManagers() and related paths wrap any user-supplied plain X509TrustManager in X509TrustManagerWrapper, which extends X509ExtendedTrustManager but implements the 3-arg checkServerTrusted(chain, authType, SSLEngine) by discarding the SSLEngine and calling the 2-arg delegate. Because the object now IS an X509ExtendedTrustManager, neither SunJSSE's internal AbstractTrustManagerWrapper nor Netty's own OpenSslX509TrustManagerWrapper will re-wrap it to add endpoint-identification. Consequently, even though Netty 4.2 sets endpointIdentificationAlgorithm="HTTPS" by default, a client built with SslContextBuilder.forClient().trustManager(somePlainX509TrustManager) performs no hostname verification at all. Versions 4.1.135.Final and 4.2.15.Final patch the issue.

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

Published

June 12, 2026

Last Modified

July 6, 2026

Advisory Details (3)

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

Wrapping plain trust manager silently disables hostname verification · Advisory · netty/netty · GitHub

https://github.com/netty/netty/security/advisories/GHSA-c653-97m9-rcg9
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-50010(6)

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
redhatnetty-handler2026-07-02redhat
redhatoffline-knowledge-portal/rhokp-rhel9:17822393702026-06-23redhat

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-handler4.0.0.Alpha1 ... 4.1.99.Final (228 versions)4.1.135.Final—

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-50010?
CVE-2026-50010 is a high 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, SimpleTrustManagerFactory.engineGetTrustManagers() and related paths wrap any user-supplied plain X509TrustManager in X509TrustManagerWrapper, which extends…
When was CVE-2026-50010 disclosed?
CVE-2026-50010 was first published in the National Vulnerability Database on June 12, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50010 actively exploited?
CVE-2026-50010 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-50010?
CVE-2026-50010 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-50010?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50010, 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-50010

Explore →

Is Your Infrastructure Affected by CVE-2026-50010?

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

Start Free Scan →Browse All CVEs