CVE-2026-47691

CRITICALNVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 10.0Exploit: None knownExposed services: Not assessed

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 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.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
45
EG 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 computed
Severity100% × 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, 2026
Patch available. Sources: github_release, github, redhat.
github Patch Available

Insufficient Bailiwick Validation for NS Records · Advisory · netty/netty · GitHub

https://github.com/netty/netty/security/advisories/GHSA-5pvg-856g-cp85
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
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-47691
redhat Patch Available

2488439 – (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=2488439

Patch Availability(10)

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)
PackageVulnerable rangeFix by version rangeDependents
netty1:4.1.48-10 ... 1:4.1.48-9 (16 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
netty1:4.1.48-10 ... 1:4.1.48-9 (12 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
netty1:4.1.48-10 ... 1:4.1.48-16 (8 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
netty1:4.1.48-10 ... 1:4.1.48-16 (7 versions)
  • every version on: no fix on record
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
io.netty:netty-resolver-dns4.1.0.Beta4 ... 4.1.99.Final (147 versions)
  • 4.2.0.Final up to 4.2.15.Final: fixed in 4.2.15.Final
  • every version up to 4.1.135.Final: fixed in 4.1.135.Final
—

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.

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

Frequently asked(5)

What is CVE-2026-47691?
CVE-2026-47691 is a critical 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 DnsResolveContext insufficiently validates the bailiwick of NS records, enabling DNS Cache Poisoning. An attacker controlling an authoritative name…
When was CVE-2026-47691 disclosed?
CVE-2026-47691 was first published on June 8, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47691 actively exploited?
CVE-2026-47691 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47691?
CVE-2026-47691 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-47691?
A fix for CVE-2026-47691 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47691 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47691

Explore →

Is Your Infrastructure Affected by CVE-2026-47691?

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