CVE-2026-47691

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.7 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-06-08) is not newer than that change (2026-09-18), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-36489 (ENISA EUVD) · GHSA-5pvg-856g-cp85 (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • 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 impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 8, 2026

Last Modified

September 18, 2026

Advisory Details (13)

Auto-updated Oct 30, 2026
Patch available. Sources: github_release, github, redhat.
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:48151
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:41951
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:37390
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:34608
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:26586
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:26018
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:26017
GitHub advisoryMentions a patch (unverified)

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
Red HatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2026-47691
Red HatMentions a patch (unverified)

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
Red HatMentions a patch (unverified)
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-47691.json

Vendor Advisories for CVE-2026-47691(20)

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

Patch Availability(19)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibnetty-java (1:4.1.48-9ubuntu0.2+esm2) @ noble2026-10-29ubuntu
redhatrhoai/odh-trustyai-service-rhel9:17917925252026-10-19redhat
redhatrh-sso7-keycloak-0:18.0.20-1.redhat_00001.1.el7sso2026-10-06redhat
redhatrh-sso7-keycloak-0:18.0.20-1.redhat_00001.1.el9sso2026-10-06redhat
redhatrh-sso7-keycloak-0:18.0.20-1.redhat_00001.1.el8sso2026-10-06redhat
redhatnetty-resolver-dns2026-10-05redhat
redhatrh-sso-7/sso76-openshift-rhel8:7.6-852026-10-05redhat
redhatrhoai/odh-trustyai-service-rhel9:17881986812026-09-08redhat
redhatdevspaces/multicluster-redirector-rhel9:17877646432026-09-01redhat
redhateap7-wildfly-0:7.4.25-2.GA_redhat_00001.1.el7eap2026-08-11redhat
redhateap7-wildfly-0:7.4.25-2.GA_redhat_00001.1.el9eap2026-08-11redhat
redhateap7-wildfly-0:7.4.25-2.GA_redhat_00001.1.el8eap2026-08-11redhat
redhateap8-wildfly-0:8.1.7.1-1.GA_redhat_00004.1.el9eap2026-08-03redhat
redhatio.netty/netty-resolver-dns:4.1.135.Final-redhat-000012026-08-03redhat
redhatcryostat/jfr-datasource-rhel9:4.2.0-132026-07-29redhat
redhatpatch2026-06-25redhat
redhatpatch2026-06-25redhat
mavenio.netty:netty-resolver-dns @ 4.2.15.Final (fixes >= 4.2.0.Final, <= 4.2.14.Final)—ghsa
mavenio.netty:netty-resolver-dns @ 4.1.135.Final (fixes <= 4.1.134.Final)—ghsa

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

(5)

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 24× in last 7d / 79× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 461 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 361 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-47691?
CVE-2026-47691 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-47691 published?
The CVE record for CVE-2026-47691 was published on June 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 18, 2026; the record at its source may have been updated since.
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 (31st 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.

Book a Demo →Browse All CVEs