Io.netty:netty resolver dns: Netty has Insufficient Bailiwick Validation for NS Records (CVE-2026-47691)
### Summary 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`). ### Details 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. This means if the resolver queries evil.co.uk., it will accept an NS record claiming authority over co.uk.. Subsequently, the `handleWithAdditional` method caches the associated A records from the ADDITIONAL section directly into the `authoritativeDnsServerCache` under the parent domain's key (co.uk.). 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 co.uk.. The `io.netty.resolver.dns.DnsResolveContext.AuthoritativeNameServerList#cache` method only prevents caching if the record is for the root zone (dots == 1). ### Impact DNS Cache Poisoning. Any application using Netty's DNS resolver is impacted.
AI Analysis
Technical Summary
The vulnerability in io.netty.resolver.dns.DnsResolveContext arises because the method that adds NS records accepts any NS record from the AUTHORITY section if the record's name is a suffix of the queried domain name. This allows an attacker controlling a subdomain's authoritative name server to inject NS records for the parent domain, bypassing standard bailiwick rules. The resolver then caches malicious A records for the parent domain, leading to DNS cache poisoning. The cache method only prevents caching for the root zone, which is insufficient. This flaw impacts all applications using Netty's DNS resolver in affected versions.
Potential Impact
This vulnerability enables DNS cache poisoning, which can lead to applications resolving domain names to attacker-controlled IP addresses. This can result in traffic interception, redirection, or other malicious activities depending on the application's use of DNS resolution. The impact is high as indicated by the CVSS score of 8.7 with high confidentiality and integrity impact and no required privileges or user interaction.
Mitigation Recommendations
A patch is available that fixes this vulnerability by upgrading Netty to version 4.1.135.Final or later. Users should apply the update provided in Red Hat build of Quarkus versions 3.27.4.SP1 or 3.33.2.SP1, which include Netty 4.1.135.Final. Before applying the update, ensure all previously released errata relevant to your system are applied. No additional mitigation is required beyond applying the official fix.
Io.netty:netty resolver dns: Netty has Insufficient Bailiwick Validation for NS Records (CVE-2026-47691)
Description
### Summary 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`). ### Details 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. This means if the resolver queries evil.co.uk., it will accept an NS record claiming authority over co.uk.. Subsequently, the `handleWithAdditional` method caches the associated A records from the ADDITIONAL section directly into the `authoritativeDnsServerCache` under the parent domain's key (co.uk.). 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 co.uk.. The `io.netty.resolver.dns.DnsResolveContext.AuthoritativeNameServerList#cache` method only prevents caching if the record is for the root zone (dots == 1). ### Impact DNS Cache Poisoning. Any application using Netty's DNS resolver is impacted.
CVSS v3.1
Score 8.7high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in io.netty.resolver.dns.DnsResolveContext arises because the method that adds NS records accepts any NS record from the AUTHORITY section if the record's name is a suffix of the queried domain name. This allows an attacker controlling a subdomain's authoritative name server to inject NS records for the parent domain, bypassing standard bailiwick rules. The resolver then caches malicious A records for the parent domain, leading to DNS cache poisoning. The cache method only prevents caching for the root zone, which is insufficient. This flaw impacts all applications using Netty's DNS resolver in affected versions.
Potential Impact
This vulnerability enables DNS cache poisoning, which can lead to applications resolving domain names to attacker-controlled IP addresses. This can result in traffic interception, redirection, or other malicious activities depending on the application's use of DNS resolution. The impact is high as indicated by the CVSS score of 8.7 with high confidentiality and integrity impact and no required privileges or user interaction.
Mitigation Recommendations
A patch is available that fixes this vulnerability by upgrading Netty to version 4.1.135.Final or later. Users should apply the update provided in Red Hat build of Quarkus versions 3.27.4.SP1 or 3.33.2.SP1, which include Netty 4.1.135.Final. Before applying the update, ensure all previously released errata relevant to your system are applied. No additional mitigation is required beyond applying the official fix.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-5pvg-856g-cp85
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-47691"]
- Ecosystems
- ["Maven"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a520efa68715ace4391e4f7
Added to database: 07/11/2026, 09:38:02 UTC
Last enriched: 08/12/2026, 18:03:52 UTC
Last updated: 09/13/2026, 10:01:31 UTC
Views: 129
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.