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.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.8Exploit: 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, 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)
EPSS
16.9%
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

Vendor Advisories for CVE-2026-45673(3)

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

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 18× in last 7d / 76× 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-06 16:27 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-05 17:25 UTCEG score recompute
  4. 2026-07-05 17:25 UTCVendor advisory
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 14:49 UTCEG score recompute
  7. 2026-07-04 14:49 UTCVendor advisory
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-03 16:10 UTCEG score recompute
  10. 2026-07-03 16:10 UTCVendor advisory
  11. 2026-07-02 12:31 UTCEG score recompute
  12. 2026-07-02 12:31 UTCVendor advisory
  13. 2026-07-01 15:07 UTCEPSS rescore
  14. 2026-07-01 14:27 UTCEG score recompute
  15. 2026-07-01 14:27 UTCVendor advisory
  16. 2026-06-30 23:22 UTCEPSS rescore
  17. 2026-06-30 16:24 UTCEG score recompute
  18. 2026-06-30 16:24 UTCVendor advisory
  19. 2026-06-29 14:47 UTCEG score recompute
  20. 2026-06-29 14:47 UTCVendor advisory
  21. 2026-06-29 14:06 UTCEPSS rescore
  22. 2026-06-29 14:06 UTCEPSS rescore
  23. 2026-06-28 16:44 UTCEG score recompute
  24. 2026-06-28 16:44 UTCVendor advisory
  25. 2026-06-28 14:07 UTCEPSS rescore
Show 51 more
  1. 2026-06-28 04:56 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-27 18:41 UTCEG score recompute
  4. 2026-06-27 18:41 UTCVendor advisory
  5. 2026-06-27 03:08 UTCEPSS rescore
  6. 2026-06-26 20:38 UTCEG score recompute
  7. 2026-06-26 20:38 UTCVendor advisory
  8. 2026-06-25 22:34 UTCEG score recompute
  9. 2026-06-25 22:34 UTCVendor advisory
  10. 2026-06-25 13:49 UTCEPSS rescore
  11. 2026-06-25 00:21 UTCEG score recompute
  12. 2026-06-25 00:21 UTCVendor advisory
  13. 2026-06-24 14:05 UTCEPSS rescore
  14. 2026-06-24 02:18 UTCEG score recompute
  15. 2026-06-24 02:18 UTCVendor advisory
  16. 2026-06-23 21:33 UTCEPSS rescore
  17. 2026-06-23 21:33 UTCEPSS rescore
  18. 2026-06-23 04:15 UTCEG score recompute
  19. 2026-06-23 04:15 UTCVendor advisory
  20. 2026-06-22 14:25 UTCEPSS rescore
  21. 2026-06-22 14:25 UTCEPSS rescore
  22. 2026-06-22 05:40 UTCEG score recompute
  23. 2026-06-22 05:40 UTCVendor advisory
  24. 2026-06-21 14:56 UTCEPSS rescore
  25. 2026-06-21 14:56 UTCEPSS rescore
  26. 2026-06-21 02:01 UTCEG score recompute
  27. 2026-06-21 02:01 UTCVendor advisory
  28. 2026-06-21 01:59 UTCEPSS rescore
  29. 2026-06-20 00:47 UTCEG score recompute
  30. 2026-06-20 00:47 UTCVendor advisory
  31. 2026-06-19 19:25 UTCEPSS rescore
  32. 2026-06-19 02:14 UTCEG score recompute
  33. 2026-06-19 02:14 UTCVendor advisory
  34. 2026-06-18 17:52 UTCEPSS rescore
  35. 2026-06-18 17:52 UTCEPSS rescore
  36. 2026-06-18 03:57 UTCEG score recompute
  37. 2026-06-17 17:53 UTCEPSS rescore
  38. 2026-06-17 05:53 UTCEG score recompute
  39. 2026-06-16 17:52 UTCEPSS rescore
  40. 2026-06-16 07:50 UTCEG score recompute
  41. 2026-06-15 17:49 UTCEPSS rescore
  42. 2026-06-15 09:48 UTCEG score recompute
  43. 2026-06-14 11:38 UTCEG score recompute
  44. 2026-06-13 23:00 UTCEPSS rescore
  45. 2026-06-13 13:35 UTCEG score recompute
  46. 2026-06-12 23:12 UTCEPSS rescore
  47. 2026-06-12 15:19 UTCEG score recompute
  48. 2026-06-11 17:15 UTCEG score recompute
  49. 2026-06-10 19:13 UTCEG score recompute
  50. 2026-06-09 21:10 UTCEG score recompute
  51. 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 16.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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.

Start Free Scan →Browse All CVEs