Skip to content
major vulnerability· requires attention

Affects a widely-used library (Netty); DNS cache poisoning could impact many Java apps, risking widespread disruption.

Networks

CVE-2026-47691

8.7
High
EPSS 0.32%Patch availableJun 13, 2026

DNS cache poisoning via bailiwick bypass in Netty DNS resolver.

common questions

Is CVE-2026-47691 being exploited?

Not confirmed. CVE-2026-47691 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.

How severe is CVE-2026-47691?

CVE-2026-47691 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-47691?

Yes. A fix has been recorded for CVE-2026-47691. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-47691 affect?

CVE-2026-47691 affects Netty < 4.1.135.Final, Netty < 4.2.15.Final, Java apps using Netty DNS resolver. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-47691?

Upgrade Netty to 4.1.135.Final or 4.2.15.Final or newer.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Netty < 4.1.135.FinalNetty < 4.2.15.FinalJava apps using Netty DNS resolver
impact

Poisoned parent-domain DNS cache; future lookups may resolve to attacker-controlled hosts, enabling spoofing and traffic redirection.

action required

Immediate action required

affected versions
netty netty
  • affected>= 4.2.0.Final and < 4.2.15.Final
  • affected< 4.1.135.Final

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free