Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-47691: Netty has Insufficient Bailiwick Validation for NS Records

CriticalCVSS 10.0 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Plan (action score 40/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: io.netty:netty-resolver-dns (Maven) 4.2.15.Final, 4.1.135.Final; netty (openSUSE:Tumbleweed) 4.1.135-1.1; eap8-eap-product-conf-parent (Red Hat:jboss_enterprise_application_platform:8.1::el10) 0:801.7.1-1.GA_redhat_00001.1.el10eap.

Add it to your regular patch cycle. Upgrade to io.netty:netty-resolver-dns (Maven) 4.2.15.Final, 4.1.135.Final; netty (openSUSE:Tumbleweed) 4.1.135-1.1; eap8-eap-product-conf-parent (Red Hat:jboss_enterprise_application_platform:8.1::el10) 0:801.7.1-1.GA_redhat_00001.1.el10eap or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Jun 12, 2026
Updated
Sep 18, 2026
EPSS
0.3% · 31th percentile

Report tools

JSON

Action score

40

Plan

Add it to your regular patch cycle.

CVSS
40 / 40 · 10.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
10.0
CNA · GitHub_M
8.7
1.3 point gap

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-47691

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
nettynetty

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • netty netty

    • >= 4.2.0.Final, < 4.2.15.Final, < 4.1.135.Finalaffected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • netty nettybefore 4.1.135
  • netty netty4.2.0 and later · before 4.2.15

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12nettyfrom 0—
Mavenio.netty:netty-resolver-dnsfrom 4.2.0.Final · before 4.2.15.Final4.2.15.Final
Mavenio.netty:netty-resolver-dnsbefore 4.1.135.Final4.1.135.Final
openSUSE:Tumbleweednettybefore 4.1.135-1.14.1.135-1.1
Red Hat:jboss_enterprise_application_platform:8.1::el10eap8-eap-product-conf-parentbefore 0:801.7.1-1.GA_redhat_00001.1.el10eap0:801.7.1-1.GA_redhat_00001.1.el10eap
Red Hat:jboss_enterprise_application_platform:8.1::el10eap8-eap-product-conf-wildfly-ee-feature-packbefore 0:801.7.1-1.GA_redhat_00001.1.el10eap0:801.7.1-1.GA_redhat_00001.1.el10eap
Red Hat:jboss_enterprise_application_platform:8.1::el10eap8-nettybefore 0:4.1.135-1.Final_redhat_00001.1.el10eap0:4.1.135-1.Final_redhat_00001.1.el10eap
Red Hat:jboss_enterprise_application_platform:8.1::el10eap8-netty-bufferbefore 0:4.1.135-1.Final_redhat_00001.1.el10eap0:4.1.135-1.Final_redhat_00001.1.el10eap
Red Hat:jboss_enterprise_application_platform:8.1::el10eap8-netty-codecbefore 0:4.1.135-1.Final_redhat_00001.1.el10eap0:4.1.135-1.Final_redhat_00001.1.el10eap
Red Hat:jboss_enterprise_application_platform:8.1::el10eap8-netty-codec-dnsbefore 0:4.1.135-1.Final_redhat_00001.1.el10eap0:4.1.135-1.Final_redhat_00001.1.el10eap
Red Hat:jboss_enterprise_application_platform:8.1::el10eap8-netty-codec-httpbefore 0:4.1.135-1.Final_redhat_00001.1.el10eap0:4.1.135-1.Final_redhat_00001.1.el10eap
Red Hat:jboss_enterprise_application_platform:8.1::el10eap8-netty-codec-socksbefore 0:4.1.135-1.Final_redhat_00001.1.el10eap0:4.1.135-1.Final_redhat_00001.1.el10eap
Red Hat:jboss_enterprise_application_platform:8.1::el10eap8-netty-commonbefore 0:4.1.135-1.Final_redhat_00001.1.el10eap0:4.1.135-1.Final_redhat_00001.1.el10eap
Red Hat:jboss_enterprise_application_platform:8.1::el10eap8-netty-handlerbefore 0:4.1.135-1.Final_redhat_00001.1.el10eap0:4.1.135-1.Final_redhat_00001.1.el10eap
Red Hat:jboss_enterprise_application_platform:8.1::el10eap8-netty-handler-proxybefore 0:4.1.135-1.Final_redhat_00001.1.el10eap0:4.1.135-1.Final_redhat_00001.1.el10eap
Red Hat:jboss_enterprise_application_platform:8.1::el10eap8-netty-resolverbefore 0:4.1.135-1.Final_redhat_00001.1.el10eap0:4.1.135-1.Final_redhat_00001.1.el10eap
Red Hat:jboss_enterprise_application_platform:8.1::el10eap8-netty-resolver-dnsbefore 0:4.1.135-1.Final_redhat_00001.1.el10eap0:4.1.135-1.Final_redhat_00001.1.el10eap
Red Hat:jboss_enterprise_application_platform:8.1::el10eap8-netty-transportbefore 0:4.1.135-1.Final_redhat_00001.1.el10eap0:4.1.135-1.Final_redhat_00001.1.el10eap
Red Hat:jboss_enterprise_application_platform:8.1::el10eap8-netty-transport-classes-epollbefore 0:4.1.135-1.Final_redhat_00001.1.el10eap0:4.1.135-1.Final_redhat_00001.1.el10eap
Red Hat:jboss_enterprise_application_platform:8.1::el10eap8-netty-transport-native-epollbefore 0:4.1.135-1.Final_redhat_00001.1.el10eap0:4.1.135-1.Final_redhat_00001.1.el10eap
Red Hat:jboss_enterprise_application_platform:8.1::el10eap8-netty-transport-native-epoll-debuginfobefore 0:4.1.135-1.Final_redhat_00001.1.el10eap0:4.1.135-1.Final_redhat_00001.1.el10eap
Red Hat:jboss_enterprise_application_platform:8.1::el10eap8-netty-transport-native-unix-commonbefore 0:4.1.135-1.Final_redhat_00001.1.el10eap0:4.1.135-1.Final_redhat_00001.1.el10eap
Red Hat:jboss_enterprise_application_platform:8.1::el10eap8-wildflybefore 0:8.1.7.1-1.GA_redhat_00004.1.el10eap0:8.1.7.1-1.GA_redhat_00004.1.el10eap
Red Hat:jboss_enterprise_application_platform:8.1::el10eap8-wildfly-java-jdk21before 0:8.1.7.1-1.GA_redhat_00004.1.el10eap0:8.1.7.1-1.GA_redhat_00004.1.el10eap

+55

Other highest-scoring records for the same primary product.

  • CVE-2026-45674Netty Vulnerable to DNS Cache Poisoning via Missing Bailiwick Checks in CNAME Records
    40Plan
  • CVE-2019-20445HttpObjectDecoder.java in Netty before 4.1.44 allows a Content-Length header to be accompanied by a second Content-Length header, or by a…
    40Plan
  • CVE-2026-42581Netty: HTTP/1.0 TE+CL Coexistence Bypasses Smuggling Sanitization
    39Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-46340Jun 12, 2026 · Netty: SCTP reassembly nests buffers without bound
    30Monitor
  • ← EarlierCVE-2026-47244Jun 12, 2026 · Netty HTTP/2: Advertised MAX_CONCURRENT_STREAMS are not enforced
    21Monitor
  • Later →CVE-2026-48006Jun 12, 2026 · Netty's Lack of Lifecycle Cleanup Leads to Pooled ByteBuf Leak in RedisArrayAggregator
    34Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Maven:io.netty:netty-resolver-dns4.1.135.FinalPackage registry (OSV)
Maven:io.netty:netty-resolver-dns4.2.15.FinalPackage registry (OSV)
opensuse:netty4.1.135-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:eap8-eap-product-conf-parent0:801.7.1-1.GA_redhat_00001.1.el10eap · Red Hat:jboss_enterprise_application_platform:8.1::el10Package registry (OSV)
red hat:eap8-eap-product-conf-wildfly-ee-feature-pack0:801.7.1-1.GA_redhat_00001.1.el10eap · Red Hat:jboss_enterprise_application_platform:8.1::el10Package registry (OSV)
red hat:eap8-netty0:4.1.135-1.Final_redhat_00001.1.el10eap · Red Hat:jboss_enterprise_application_platform:8.1::el10Package registry (OSV)
red hat:eap8-netty-buffer0:4.1.135-1.Final_redhat_00001.1.el10eap · Red Hat:jboss_enterprise_application_platform:8.1::el10Package registry (OSV)
red hat:eap8-netty-codec0:4.1.135-1.Final_redhat_00001.1.el10eap · Red Hat:jboss_enterprise_application_platform:8.1::el10Package registry (OSV)
red hat:eap8-netty-codec-dns0:4.1.135-1.Final_redhat_00001.1.el10eap · Red Hat:jboss_enterprise_application_platform:8.1::el10Package registry (OSV)
red hat:eap8-netty-codec-http0:4.1.135-1.Final_redhat_00001.1.el10eap · Red Hat:jboss_enterprise_application_platform:8.1::el10Package registry (OSV)
red hat:eap8-netty-codec-socks0:4.1.135-1.Final_redhat_00001.1.el10eap · Red Hat:jboss_enterprise_application_platform:8.1::el10Package registry (OSV)
red hat:eap8-netty-common0:4.1.135-1.Final_redhat_00001.1.el10eap · Red Hat:jboss_enterprise_application_platform:8.1::el10Package registry (OSV)
red hat:eap8-netty-handler0:4.1.135-1.Final_redhat_00001.1.el10eap · Red Hat:jboss_enterprise_application_platform:8.1::el10Package registry (OSV)
red hat:eap8-netty-handler-proxy0:4.1.135-1.Final_redhat_00001.1.el10eap · Red Hat:jboss_enterprise_application_platform:8.1::el10Package registry (OSV)
red hat:eap8-netty-resolver0:4.1.135-1.Final_redhat_00001.1.el10eap · Red Hat:jboss_enterprise_application_platform:8.1::el10Package registry (OSV)
suse:netty4.1.135-150200.4.50.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP7Package registry (OSV)
suse:netty-tcnative2.0.79-150200.3.45.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-456740 days apartNetty Vulnerable to DNS Cache Poisoning via Missing Bailiwick Checks in CNAME Records
    40Plan

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

nvd-primary

References

All records