{"document":{"category":"csaf_vex","csaf_version":"2.0","title":"CVE-2026-47691: Netty has Insufficient Bailiwick Validation for NS Records","publisher":{"category":"vendor","name":"HarborGuard Database","namespace":"https://database.harborguard.co"},"tracking":{"id":"CVE-2026-47691","status":"final","version":"1","initial_release_date":"2026-06-12T14:33:16.595Z","current_release_date":"2026-06-13T03:56:03.157Z","revision_history":[{"date":"2026-06-12T14:33:16.595Z","number":"1","summary":"Initial machine-readable export from HarborGuard."}]},"distribution":{"tlp":{"label":"WHITE"},"text":"Public CVE data; freely redistributable."},"notes":[{"category":"description","text":"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.","title":"CVE description"}],"references":[{"category":"self","summary":"CVE-2026-47691 on HarborGuard Database","url":"https://database.harborguard.co/cve/CVE-2026-47691"},{"category":"external","summary":"CVE Record","url":"https://www.cve.org/CVERecord?id=CVE-2026-47691"},{"category":"external","summary":"https://github.com/netty/netty/security/advisories/GHSA-5pvg-856g-cp85","url":"https://github.com/netty/netty/security/advisories/GHSA-5pvg-856g-cp85"},{"category":"external","summary":"https://github.com/netty/netty/releases/tag/netty-4.1.135.Final","url":"https://github.com/netty/netty/releases/tag/netty-4.1.135.Final"},{"category":"external","summary":"https://github.com/netty/netty/releases/tag/netty-4.2.15.Final","url":"https://github.com/netty/netty/releases/tag/netty-4.2.15.Final"}]},"product_tree":{"branches":[{"category":"vendor","name":"netty","branches":[{"category":"product_name","name":"netty","branches":[{"category":"product_version","name":">= 4.2.0.Final, < 4.2.15.Final","product":{"name":"netty netty >= 4.2.0.Final, < 4.2.15.Final","product_id":"CSAFPID-1","product_identification_helper":{"cpe":"cpe:2.3:a:netty:netty:*:*:*:*:*:*:*:*"}}},{"category":"product_version","name":"< 4.1.135.Final","product":{"name":"netty netty < 4.1.135.Final","product_id":"CSAFPID-2","product_identification_helper":{"cpe":"cpe:2.3:a:netty:netty:*:*:*:*:*:*:*:*"}}}]}]}]},"vulnerabilities":[{"cve":"CVE-2026-47691","title":"Netty has Insufficient Bailiwick Validation for NS Records","notes":[{"category":"description","text":"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.","title":"CVE description"}],"product_status":{"known_affected":["CSAFPID-1","CSAFPID-2"]},"scores":[{"cvss_v3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N","baseScore":8.7,"baseSeverity":"HIGH"},"products":["CSAFPID-1","CSAFPID-2"]}],"remediations":[{"category":"none_available","details":"No fixed version is published yet. Monitor the upstream advisory.","product_ids":["CSAFPID-1","CSAFPID-2"]}]}]}