CVE-2026-45674: Netty Vulnerable to DNS Cache Poisoning via Missing Bailiwick Checks in CNAME Records

Published Jun 8, 2026
·
Updated

Summary Netty's DnsResolveContext fails to validate the origin (bailiwick) of CNAME records in DNS responses.

Details In io.netty.resolver.dns.DnsResolveContext#buildAliasMap, the resolver processes the ANSWER section of a DNS response and blindly caches all CNAME records it finds.

According to https://datatracker.ietf.org/doc/html/rfc5452#section-6

Care must be taken to only accept data if it is known that the originator is authoritative for the QNAME or a parent of the QNAME. One very simple way to achieve this is to only accept data if it is part of the domain for which the query was intended.

Impact DNS Cache Poisoning (Bailiwick Bypass). Any application using Netty's DNS resolver is impacted.

Other sources

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 fails to validate the origin (bailiwick) of CNAME records in DNS responses. Versions 4.1.135.Final and 4.2.15.Final patch the issue.

MITRE

Affected Software

5 affected componentsFixes available
maven/io.netty:netty-resolver-dns<=4.1.134.Final
4.1.135.Final
maven/io.netty:netty-resolver-dns>=4.2.0.Final<=4.2.14.Final
4.2.15.Final
Netty Netty<4.1.135
Netty Netty>=4.2.0<4.2.15
IBM Netezza Software<=11.3.0.3-IF2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/io.netty:netty-resolver-dns to a version that resolves this vulnerability.

    Fixed in 4.1.135.Final
  2. Upgrade

    Upgrade maven/io.netty:netty-resolver-dns to a version that resolves this vulnerability.

    Fixed in 4.2.15.Final
  3. Upgrade

    Upgrade io.netty.resolver.dns.DnsResolveContext to a version that resolves this vulnerability.

    Fixed in 4.1.135.Final
  4. Upgrade

    Upgrade io.netty.resolver.dns.DnsResolveContext to a version that resolves this vulnerability.

    Fixed in 4.2.15.Final

Event History

Jun 8, 2026
Advisory Published
via GitHub·11:02 PM
Data Sourced
via GitHub·11:02 PM
DescriptionSeverityWeaknessAffected Software
Jun 12, 2026
CVE Published
via MITRE·02:17 PM
Data Sourced
via MITRE·02:17 PM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·03:02 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·03:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:16 PM
Affected Software
Aug 20, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2026-45674?

CVE-2026-45674 has a high severity rating of 8.7.

2

How do I fix CVE-2026-45674?

To mitigate CVE-2026-45674, update to the latest version of Netty that addresses this issue.

3

What does CVE-2026-45674 affect?

CVE-2026-45674 affects the Netty library specifically the netty-resolver-dns component.

4

What exploit does CVE-2026-45674 represent?

CVE-2026-45674 allows for DNS responses to be exploited due to improper validation of CNAME records.

5

When was CVE-2026-45674 published?

CVE-2026-45674 was published on June 8, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203