CVE-2026-45673

MEDIUMPre-NVD 6.86.8
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 83% 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
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.8Exploit: None knownExposed: 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, Netty's DNS resolver uses a predictable PRNG for generating DNS transaction IDs and defaults to a static UDP source port. This combination reduces the entropy of DNS queries, enabling DNS Cache Poisoning (Kaminsky attack). Versions 4.1.135.Final and 4.2.15.Final patch the issue.

CVSS v3
6.8
EG Score
6.8(medium)
EG Risk
31(Track)
EG Risk 31/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
Severity68% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

June 8, 2026

Last Modified

June 15, 2026

Advisory Details (3)

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

DNS Cache Poisoning due to Predictable PRNG and Default Static Source Port · Advisory · netty/netty · GitHub

https://github.com/netty/netty/security/advisories/GHSA-xmv7-r254-6q78
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(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnetty-resolver-dns2026-06-17redhat

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-resolver-dns4.1.0.Beta4 ... 4.1.99.Final (147 versions)4.1.135.Final

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× 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.

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

Frequently asked(5)

What is CVE-2026-45673?
CVE-2026-45673 is a medium 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, Netty's DNS resolver uses a predictable PRNG for generating DNS transaction IDs and defaults to a static UDP source port. This combination reduces the entropy…
When was CVE-2026-45673 disclosed?
CVE-2026-45673 was first published in the National Vulnerability Database on June 8, 2026, with the most recent update on June 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45673 actively exploited?
CVE-2026-45673 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 82.8% of all scored CVEs.
What is the CVSS score of CVE-2026-45673?
CVE-2026-45673 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-45673?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45673, 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-45673

Explore →

Is Your Infrastructure Affected by CVE-2026-45673?

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