{"items":[{"id":"NVI-00013938","kind":"vulnerability","title":"Netty Vulnerable to DNS Cache Poisoning via Missing Bailiwick Checks in CNAME Records","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-676x-f7gg-47vc","CVE-2026-45674"],"plain_summary":"GitHub lists this reviewed advisory for io.netty:netty-resolver-dns, io.netty:netty-resolver-dns. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-0d627de589828639f3cc0891e6575d69"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-09-18T15:32:44.000Z","value":"8.7 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-207bfee29ed239f1344194bf8a4f3c07"},{"kind":"EPSS","as_of":"2026-11-04T12:03:12.000Z","value":"0.292%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.21896. Missing scores are unknown.","source_id":"sr-0d627de589828639f3cc0891e6575d69"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-207bfee29ed239f1344194bf8a4f3c07","url":"https://github.com/advisories/GHSA-676x-f7gg-47vc","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-676x-f7gg-47vc","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T14:29:49.409Z"},{"id":"sr-0d627de589828639f3cc0891e6575d69","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-45674","publisher":"FIRST EPSS","observed_at":"2026-11-04T17:58:50.328Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-207bfee29ed239f1344194bf8a4f3c07"],"technology":"io.netty:netty-resolver-dns","known_exclusions":[],"conditions_summary":"### Summary\nNetty's DnsResolveContext fails to validate the origin (bailiwick) of CNAME records in DNS responses.\n\n### Details\nIn `io.netty.resolver.dns.DnsResolveContext#buildAliasMap`, the resolver processes the ANSWER section of a DNS response and blindly caches all CNAME records it finds.\n\nAccording to https://datatracker.ietf.org/doc/html/rfc5452#section-6 \n\n```\nCare must be taken to only accept\n   data if it is known that the originator is authoritative for the\n   QNAME or a parent of the QNAME.\n   One very simple way to achieve this is to only accept data if it is\n   part of the domain for which the query was intended.\n```\n\n### Impact\nDNS Cache Poisoning (Bailiwick Bypass). Any application using Netty's DNS resolver is impacted.","public_affected_ranges":[">= 4.2.0.Final, <= 4.2.14.Final"]},{"certainty":"source_listed","source_ids":["sr-207bfee29ed239f1344194bf8a4f3c07"],"technology":"io.netty:netty-resolver-dns","known_exclusions":[],"conditions_summary":"### Summary\nNetty's DnsResolveContext fails to validate the origin (bailiwick) of CNAME records in DNS responses.\n\n### Details\nIn `io.netty.resolver.dns.DnsResolveContext#buildAliasMap`, the resolver processes the ANSWER section of a DNS response and blindly caches all CNAME records it finds.\n\nAccording to https://datatracker.ietf.org/doc/html/rfc5452#section-6 \n\n```\nCare must be taken to only accept\n   data if it is known that the originator is authoritative for the\n   QNAME or a parent of the QNAME.\n   One very simple way to achieve this is to only accept data if it is\n   part of the domain for which the query was intended.\n```\n\n### Impact\nDNS Cache Poisoning (Bailiwick Bypass). Any application using Netty's DNS resolver is impacted.","public_affected_ranges":["<= 4.1.134.Final"]}],"null_published_at":"2026-11-07T14:01:58.758Z","source_updated_at":"2026-09-18T15:32:44.000Z","source_disclosed_at":"2026-06-08T23:02:26.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-11-01T14:29:49.409Z"},{"id":"NVI-00013938","kind":"vulnerability","title":"Netty Vulnerable to DNS Cache Poisoning via Missing Bailiwick Checks in CNAME Records","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-676x-f7gg-47vc","CVE-2026-45674"],"plain_summary":"GitHub lists this reviewed advisory for io.netty:netty-resolver-dns, io.netty:netty-resolver-dns. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-207bfee29ed239f1344194bf8a4f3c07"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-09-18T15:32:44.000Z","value":"8.7 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-207bfee29ed239f1344194bf8a4f3c07"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-207bfee29ed239f1344194bf8a4f3c07","url":"https://github.com/advisories/GHSA-676x-f7gg-47vc","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-676x-f7gg-47vc","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T14:29:49.409Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-207bfee29ed239f1344194bf8a4f3c07"],"technology":"io.netty:netty-resolver-dns","known_exclusions":[],"conditions_summary":"### Summary\nNetty's DnsResolveContext fails to validate the origin (bailiwick) of CNAME records in DNS responses.\n\n### Details\nIn `io.netty.resolver.dns.DnsResolveContext#buildAliasMap`, the resolver processes the ANSWER section of a DNS response and blindly caches all CNAME records it finds.\n\nAccording to https://datatracker.ietf.org/doc/html/rfc5452#section-6 \n\n```\nCare must be taken to only accept\n   data if it is known that the originator is authoritative for the\n   QNAME or a parent of the QNAME.\n   One very simple way to achieve this is to only accept data if it is\n   part of the domain for which the query was intended.\n```\n\n### Impact\nDNS Cache Poisoning (Bailiwick Bypass). Any application using Netty's DNS resolver is impacted.","public_affected_ranges":[">= 4.2.0.Final, <= 4.2.14.Final"]},{"certainty":"source_listed","source_ids":["sr-207bfee29ed239f1344194bf8a4f3c07"],"technology":"io.netty:netty-resolver-dns","known_exclusions":[],"conditions_summary":"### Summary\nNetty's DnsResolveContext fails to validate the origin (bailiwick) of CNAME records in DNS responses.\n\n### Details\nIn `io.netty.resolver.dns.DnsResolveContext#buildAliasMap`, the resolver processes the ANSWER section of a DNS response and blindly caches all CNAME records it finds.\n\nAccording to https://datatracker.ietf.org/doc/html/rfc5452#section-6 \n\n```\nCare must be taken to only accept\n   data if it is known that the originator is authoritative for the\n   QNAME or a parent of the QNAME.\n   One very simple way to achieve this is to only accept data if it is\n   part of the domain for which the query was intended.\n```\n\n### Impact\nDNS Cache Poisoning (Bailiwick Bypass). Any application using Netty's DNS resolver is impacted.","public_affected_ranges":["<= 4.1.134.Final"]}],"null_published_at":"2026-11-02T10:00:37.176Z","source_updated_at":"2026-09-18T15:32:44.000Z","source_disclosed_at":"2026-06-08T23:02:26.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-01T14:29:49.409Z"}],"next_cursor":null,"snapshot_revision":"42594"}