CVE-2026-47691

Netty has Insufficient Bailiwick Validation for NS Records

CRITICAL
10
CVSS Score
Published: June 12, 2026 at 02:33 PM UTC
Updated: September 18, 2026 at 02:29 PM UTC
9 products affected across 2 vendorsNettyFuseJBoss Enterprise Application Platform Expansion Pack

Using netty by netty?

Get instant alerts when new vulnerabilities affect netty - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
CRITICAL10
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 4.1.135v < 4.1.135.Finalv < 4.2.15.Final4.2.0 ≤ v < 4.2.15
Affected range stops below 4.1.135, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.1.135.Final, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.2.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.2.15.Final, so it looks safe — our inference, not a vendor statement
All versions
Vendor states this is fixed in 1787764643 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (23)

x_refsource_CONFIRMVendor Advisory
Source: cverecord
https://github.com/netty/netty/security/advisories/GHSA-5pvg-856g-cp85
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/netty/netty/releases/tag/netty-4.1.135.Final
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/netty/netty/releases/tag/netty-4.2.15.Final
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:26017
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:26018
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:26586
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/security/cve/CVE-2026-47691
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://bugzilla.redhat.com/show_bug.cgi?id=2488439

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-345CWE-346

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card