CVE-2026-62243

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-22. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Netty (io.netty:netty-handler) versions from 4.2.0.Final through 4.2.16.Final and versions through 4.1.136.Final disable TLS hostname verification on the SslProvider.OPENSSL client path when a plain (non-extended) X509TrustManager is used and Unsafe-based trust-manager wrapping is unavailable (Java 25+). In this configuration the OpenSSL client does not perform hostname verification, allowing a man-in-the-middle attacker to present a certificate issued for a different hostname that is accepted without validation. Fixed in 4.2.17.Final and 4.1.137.Final.

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

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%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 22, 2026

Last Modified

September 10, 2026

Advisory Details (2)

Auto-updated Aug 22, 2026
Patch available. Sources: github.
generic

Netty 4.2.0 through 4.2.16 TLS Hostname Verification Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/netty-through-tls-hostname-verification-bypass
githubMentions a patch (unverified)

Hostname verification disabled on the OpenSSL client path when trust-manager wrapping is unavailable (Java 25+) · Advisory · netty/netty · GitHub

https://github.com/netty/netty/security/advisories/GHSA-p85m-gvr3-788c

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatnetty-handler2026-09-24redhat
redhateap8-xml-security-0:3.0.6-1.redhat_00001.1.el9eap2026-09-22redhat
redhateap8-xml-security-0:3.0.6-1.redhat_00001.1.el10eap2026-09-22redhat
redhateap8-xml-security-0:3.0.6-1.redhat_00001.1.el8eap2026-09-22redhat
redhatrhbk/keycloak-rhel9-operator:26.4-262026-09-16redhat
redhatrhbk/keycloak-rhel9-operator2026-09-16redhat
redhatrhbk/keycloak-rhel9-operator:26.6-202026-09-16redhat

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

(3 across 3 ecosystems)
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
—

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 31× in last 7d / 149× 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 229 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-62243?
CVE-2026-62243 is a high vulnerability published on August 22, 2026. Netty (io.netty:netty-handler) versions from 4.2.0.Final through 4.2.16.Final and versions through 4.1.136.Final disable TLS hostname verification on the SslProvider.OPENSSL client path when a plain (non-extended) X509TrustManager is used and Unsafe-based trust-manager wrapping is unavailable (Java…
When was CVE-2026-62243 disclosed?
CVE-2026-62243 was first published on August 22, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62243 actively exploited?
CVE-2026-62243 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62243?
CVE-2026-62243 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-62243?
A fix for CVE-2026-62243 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-62243 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-62243

Explore →

Is Your Infrastructure Affected by CVE-2026-62243?

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