CVE-2026-44249

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 56% 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
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: None knownExposed: 0

A fix is available — apply it.

Netty is a network application framework for development of protocol servers and clients. In netty-handler prior to versions 4.1.135.Final and 4.2.15.Final, an attacker can bypass IPv6 subnet rules due to an incorrect masking operation in IpSubnetFilterRule.compareTo(). Valid public IP addresses can bypass the restrictions. Versions 4.1.135.Final and 4.2.15.Final patch the issue.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

June 8, 2026

Last Modified

July 23, 2026

Advisory Details (3)

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

IPv6 Subnet Filter Bypass via Incorrect Comparator Masking · Advisory · netty/netty · GitHub

https://github.com/netty/netty/security/advisories/GHSA-3qp7-7mw8-wx86
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-44249(9)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnetty-handler2026-07-20redhat
redhatdevspaces/pluginregistry-rhel9:17829893672026-07-08redhat
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(3)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 63× 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 101 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-44249?
CVE-2026-44249 is a high vulnerability published on June 8, 2026. Netty is a network application framework for development of protocol servers and clients. In netty-handler prior to versions 4.1.135.Final and 4.2.15.Final, an attacker can bypass IPv6 subnet rules due to an incorrect masking operation in IpSubnetFilterRule.compareTo(). Valid public IP addresses…
When was CVE-2026-44249 disclosed?
CVE-2026-44249 was first published in the National Vulnerability Database on June 8, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44249 actively exploited?
CVE-2026-44249 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.1% of all scored CVEs.
What is the CVSS score of CVE-2026-44249?
CVE-2026-44249 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-44249?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44249, 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-44249

Explore →

Is Your Infrastructure Affected by CVE-2026-44249?

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

Start Free Scan →Browse All CVEs