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 DnsResolveContext fails to validate the origin (bailiwick) of CNAME records in DNS responses. Versions 4.1.135.Final and 4.2.15.Final patch the issue.
CVE-2026-45674
This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 87% 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).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 10.0
- EG Score
- 10.0(medium)
- EG Risk
- 45(Track)EG Risk 45/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 computedSeverity100% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 13%
- KEV
- Not listed
Published
June 8, 2026
Last Modified
July 21, 2026
Advisory Details (12)
Auto-updated Jul 21, 2026DNS Cache Poisoning via Missing Bailiwick Checks in CNAME Records · Advisory · netty/netty · GitHub
https://github.com/netty/netty/security/advisories/GHSA-676x-f7gg-47vcnetty-4.2.15.Final
Patch available: netty/netty netty-4.2.15.Final
https://github.com/netty/netty/releases/tag/netty-4.2.15.Finalnetty-4.1.135.Final
Patch available: netty/netty netty-4.1.135.Final
https://github.com/netty/netty/releases/tag/netty-4.1.135.Final2488400 – (CVE-2026-45674) CVE-2026-45674 netty-resolver-dns: Netty: Information disclosure and data manipulation due to improper CNAME record validation
https://bugzilla.redhat.com/show_bug.cgi?id=2488400Vendor Advisories for CVE-2026-45674(7)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:41951Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Data Grid 8.6.2 security update
- RHSA-2026:37390Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Build of Apache Camel 4.18.1.P1 for Spring Boot release.
- RHSA-2026:34608Red Hat Product SecurityHigh
Red Hat Security Advisory: Streams for Apache Kafka 2.9.4 release and security update
- RHSA-2026:26586Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat build of Apache Camel 4.18 for Quarkus 3.33 security update
- RHSA-2026:26018Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat build of Quarkus 3.27.4.SP1 security update
- RHSA-2026:26017Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat build of Quarkus 3.33.2.SP1 security update
- GHSA-676x-f7gg-47vcGitHub Security AdvisoriesHigh
Netty Vulnerable to DNS Cache Poisoning via Missing Bailiwick Checks in CNAME Records
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | netty-resolver-dns | 2026-07-20 | redhat |
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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| io.netty:netty-resolver-dns | 4.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 13× in last 7d / 97× 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 145 total refreshes for this CVE.
- 2026-07-27 08:31 UTCVendor advisory
- 2026-07-27 02:01 UTCVendor advisory
- 2026-07-26 21:40 UTCEG score recompute
- 2026-07-26 21:40 UTCVendor advisory
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:16 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 09:39 UTCVendor advisory
- 2026-07-16 05:26 UTCVendor advisory
- 2026-07-16 00:23 UTCVendor advisory
- 2026-07-15 20:31 UTCVendor advisory
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:26 UTCNVD updateCVSS v3 → 10 · severity → CRITICAL
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 01:21 UTCMITRE cvelistV5CVSS v3 → 8.7 · severity → HIGH
Show 75 moreShow fewer
- 2026-07-14 21:23 UTCVendor advisory
- 2026-07-14 16:39 UTCVendor advisory
- 2026-07-14 12:46 UTCVendor advisory
- 2026-07-14 02:43 UTCVendor advisory
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 09:53 UTCVendor advisory
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 05:18 UTCVendor advisory
- 2026-07-12 00:15 UTCVendor advisory
- 2026-07-11 20:23 UTCVendor advisory
- 2026-07-11 16:31 UTCVendor advisory
- 2026-07-11 12:37 UTCVendor advisory
- 2026-07-11 08:45 UTCVendor advisory
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 04:49 UTCVendor advisory
- 2026-07-10 21:24 UTCEG score recompute▲ 1.30
- 2026-07-10 21:24 UTCVendor advisory
- 2026-07-10 12:27 UTCNVD updateCVSS v3 → 10 · severity → CRITICAL
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 04:00 UTCVendor advisory
- 2026-07-08 15:52 UTCVendor advisory
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 02:38 UTCEG score recompute▼ 1.30
- 2026-07-08 02:38 UTCVendor advisory
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 13:07 UTCMITRE cvelistV5CVSS v3 → 8.7 · severity → HIGH
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 01:44 UTCVendor advisory
- 2026-07-05 21:52 UTCVendor advisory
- 2026-07-05 17:24 UTCVendor advisory
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 00:53 UTCVendor advisory
- 2026-07-04 20:06 UTCVendor advisory
- 2026-07-04 14:50 UTCVendor advisory
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 23:55 UTCVendor advisory
- 2026-07-03 20:03 UTCVendor advisory
- 2026-07-03 16:09 UTCVendor advisory
- 2026-07-03 09:21 UTCVendor advisory
- 2026-07-03 03:18 UTCVendor advisory
- 2026-07-02 23:22 UTCVendor advisory
- 2026-07-02 19:28 UTCVendor advisory
- 2026-07-02 15:36 UTCVendor advisory
- 2026-07-02 11:23 UTCVendor advisory
- 2026-07-02 07:24 UTCVendor advisory
- 2026-07-02 03:21 UTCVendor advisory
- 2026-07-01 23:29 UTCVendor advisory
- 2026-07-01 19:37 UTCVendor advisory
- 2026-07-01 15:46 UTCVendor advisory
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 11:54 UTCVendor advisory
- 2026-07-01 08:02 UTCVendor advisory
- 2026-07-01 04:11 UTCVendor advisory
- 2026-07-01 00:16 UTCVendor advisory
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 20:16 UTCVendor advisory
- 2026-06-30 16:24 UTCEG score recompute▲ 1.30
- 2026-06-30 16:24 UTCVendor advisory
- 2026-06-30 04:33 UTCNVD updateCVSS v3 → 10 · severity → CRITICAL
- 2026-06-30 01:48 UTCVendor advisory
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 13:40 UTCVendor advisory
- 2026-06-29 01:31 UTCVendor advisory
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 13:23 UTCVendor advisory
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 01:14 UTCVendor advisory
- 2026-06-27 13:06 UTCVendor advisory
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-27 00:56 UTCVendor advisory
- 2026-06-26 12:45 UTCVendor advisory
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p90HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Same CWE
10 shownCWE-345 · CWE-346
Frequently asked(5)
What is CVE-2026-45674?
When was CVE-2026-45674 disclosed?
Is CVE-2026-45674 actively exploited?
What is the CVSS score of CVE-2026-45674?
How do I remediate CVE-2026-45674?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45674
Is Your Infrastructure Affected by CVE-2026-45674?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.