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 insufficiently validates the bailiwick of NS records, enabling DNS Cache Poisoning. An attacker controlling an authoritative name server for a subdomain can poison the cache for parent domains (like .co.uk). In io.netty.resolver.dns.DnsResolveContext.AuthoritativeNameServerList#add method accepts any NS record from the AUTHORITY section as long as the record's name is a suffix of the questionName. Subsequently, the handleWithAdditional method caches the associated A records from the ADDITIONAL section directly into the authoritativeDnsServerCache under the parent domain's key. This bypasses standard bailiwick rules, where a server authoritative for a subdomain should not be trusted to provide authoritative records for its parent. The poisoned cache is then used for all future resolutions under the parent domain's key. Versions 4.1.135.Final and 4.2.15.Final patch the issue.
CVE-2026-47691
This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 75% 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.0CRITICALmedium confidence
- EG Risk
- 45EG Risk 45/100
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% - EPSS PROB
- 0.4%
- EPSS %ILE
- 27th
- KEV
- Not listed
Published
June 8, 2026
Last Modified
September 18, 2026
Advisory Details (13)
Auto-updated Oct 2, 2026Insufficient Bailiwick Validation for NS Records · Advisory · netty/netty · GitHub
https://github.com/netty/netty/security/advisories/GHSA-5pvg-856g-cp85netty-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.Final2488439 – (CVE-2026-47691) CVE-2026-47691 io.netty/netty-resolver-dns: Netty has Insufficient Bailiwick Validation for NS Records
https://bugzilla.redhat.com/show_bug.cgi?id=2488439Vendor Advisories for CVE-2026-47691(18)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:65126Red Hat Product SecurityHigh
Red Hat Security Advisory: RHOAI 2.25.11 - Red Hat OpenShift AI
- RHSA-2026:62260Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat OpenShift Dev Spaces 3.30.0 Release.
- RHSA-2026:54435Red Hat Product SecurityHigh
Red Hat Security Advisory: Streams for Apache Kafka 3.2.1 release and security update
- RHSA-2026:53806Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4.25 security update
- RHSA-2026:53646Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4.25 Security update
- RHSA-2026:53645Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4.25 Security update
- RHSA-2026:53644Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4.25 security pdate
- RHSA-2026:50085Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 8.1.7.1 XP 6.0.5.1 release
- +10 more
Patch Availability(10)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libnetty-java (1:4.1.48-9ubuntu0.2+esm2) @ noble | 2026-09-18 | ubuntu |
| redhat | rhoai/odh-trustyai-service-rhel9:1788198681 | 2026-09-08 | redhat |
| redhat | devspaces/multicluster-redirector-rhel9:1787764643 | 2026-09-01 | redhat |
| redhat | netty-resolver-dns | 2026-08-12 | redhat |
| redhat | eap7-wildfly-0:7.4.25-2.GA_redhat_00001.1.el8eap | 2026-08-11 | redhat |
| redhat | eap7-wildfly-0:7.4.25-2.GA_redhat_00001.1.el7eap | 2026-08-11 | redhat |
| redhat | eap7-wildfly-0:7.4.25-2.GA_redhat_00001.1.el9eap | 2026-08-11 | redhat |
| redhat | eap8-wildfly-0:8.1.7.1-1.GA_redhat_00004.1.el9eap | 2026-08-03 | redhat |
| redhat | io.netty/netty-resolver-dns:4.1.135.Final-redhat-00001 | 2026-08-03 | redhat |
| redhat | cryostat/jfr-datasource-rhel9:4.2.0-13 | 2026-07-29 | 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
(5 across 5 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| netty | 1:4.1.48-10 ... 1:4.1.48-9 (16 versions) |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| netty | 1:4.1.48-10 ... 1:4.1.48-9 (12 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| netty | 1:4.1.48-10 ... 1:4.1.48-16 (8 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| netty | 1:4.1.48-10 ... 1:4.1.48-16 (7 versions) |
| — |
Maven(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| io.netty:netty-resolver-dns | 4.1.0.Beta4 ... 4.1.99.Final (147 versions) |
| — |
Weakness Classification(2)
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 5× in last 7d / 30× 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 384 total refreshes for this CVE.
- 2026-10-04 23:22 UTCEPSS rescore
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-09-30 15:03 UTCEPSS rescore
- 2026-09-28 13:51 UTCEPSS rescore
- 2026-09-27 13:48 UTCEPSS rescore
- 2026-09-26 15:59 UTCEPSS rescore
- 2026-09-26 00:27 UTCEPSS rescore
- 2026-09-23 17:53 UTCEPSS rescore
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 13:23 UTCVendor advisory
- 2026-09-18 12:19 UTCEG score recompute
- 2026-09-18 12:19 UTCVendor advisory
- 2026-09-17 12:10 UTCEG score recompute
- 2026-09-17 12:10 UTCVendor advisory
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-14 08:52 UTCVendor advisory
- 2026-09-14 04:47 UTCEG score recompute
- 2026-09-14 04:47 UTCVendor advisory
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 13:40 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-09 12:38 UTCEG score recompute
- 2026-09-09 12:38 UTCVendor advisory
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-02 13:38 UTCVendor advisory
- 2026-09-02 12:38 UTCEG score recompute
- 2026-09-02 12:38 UTCVendor advisory
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-08-31 01:35 UTCEG score recompute
- 2026-08-31 01:35 UTCVendor advisory
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 05:09 UTCVendor advisory
- 2026-08-25 01:12 UTCEG score recompute
- 2026-08-25 01:12 UTCVendor advisory
- 2026-08-23 23:46 UTCVendor advisory
- 2026-08-23 19:30 UTCVendor advisory
- 2026-08-23 15:33 UTCVendor advisory
- 2026-08-23 11:36 UTCEG score recompute
- 2026-08-23 11:36 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEG score recompute
- 2026-08-21 23:49 UTCVendor advisory
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 19:52 UTCVendor advisory
- 2026-08-21 13:22 UTCVendor advisory
- 2026-08-21 12:25 UTCVendor advisory
- 2026-08-21 06:41 UTCVendor advisory
- 2026-08-21 02:11 UTCEG score recompute
- 2026-08-21 02:11 UTCVendor advisory
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 21:51 UTCVendor advisory
- 2026-08-20 17:54 UTCVendor advisory
- 2026-08-20 13:57 UTCVendor advisory
- 2026-08-20 12:42 UTCVendor advisory
- 2026-08-20 09:26 UTCEG score recompute
- 2026-08-20 09:26 UTCVendor advisory
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 14:38 UTCEG score recompute
- 2026-08-17 14:38 UTCVendor advisory
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 10:38 UTCVendor advisory
- 2026-08-17 06:39 UTCVendor advisory
- 2026-08-17 01:43 UTCVendor advisory
- 2026-08-16 17:03 UTCEG score recompute
- 2026-08-16 17:03 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 13:06 UTCVendor advisory
- 2026-08-16 09:09 UTCVendor advisory
- 2026-08-16 04:57 UTCEG score recompute
- 2026-08-16 04:57 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-16 01:00 UTCVendor advisory
- 2026-08-15 15:43 UTCVendor advisory
- 2026-08-15 11:45 UTCVendor advisory
- 2026-08-15 02:07 UTCEG score recompute
- 2026-08-15 02:07 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 22:11 UTCVendor advisory
- 2026-08-14 18:10 UTCVendor advisory
- 2026-08-14 14:13 UTCVendor advisory
- 2026-08-14 10:16 UTCVendor advisory
- 2026-08-14 06:19 UTCVendor advisory
- 2026-08-14 02:23 UTCVendor advisory
- 2026-08-13 22:26 UTCEG score recompute
- 2026-08-13 22:26 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownMaven:io.netty:netty-resolver-dns · Debian:11:netty
- CVE-2026-45674EG 10.0CRITICAL
- CVE-2026-45673EG 6.8MEDIUM
- CVE-2026-56817EG 9.8CRITICAL
- CVE-2026-42581EG 9.8CRITICAL
- CVE-2026-56820EG 9.1CRITICAL
- CVE-2026-42584EG 9.1CRITICAL
- CVE-2026-42579EG 9.1CRITICAL
- CVE-2019-20445EG 9.1EPSS p96CRITICAL
- CVE-2019-20444EG 9.1EPSS p95CRITICAL
- CVE-2023-44487NVD 7.5EG 9.0 KEVEPSS p100CRITICAL
Same vendor
10 shownredhat:RHSA-2026:26017 · redhat:RHSA-2026:34608 · redhat:RHSA-2026:37390
Frequently asked(5)
What is CVE-2026-47691?
When was CVE-2026-47691 disclosed?
Is CVE-2026-47691 actively exploited?
What is the CVSS score of CVE-2026-47691?
How do I remediate CVE-2026-47691?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47691
Is Your Infrastructure Affected by CVE-2026-47691?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.