CVE-2025-40778: DNS Cache Poisoning via Unsolicited Resource Records in ISC BIND 9
CVE-2025-40778 is a DNS cache-poisoning vulnerability in ISC BIND 9 caused by overly permissive acceptance of resource records from DNS responses. Insufficient record checking can allow unsolicited or forged records to enter a recursive resolver's cache. In shared-zone hosting scenarios, a response associated with an attacker-controlled subdomain can introduce malicious records for the zone apex or sibling domains, undermining isolation between independently controlled names. Affected versions are 9.11.0–9.16.50, 9.18.0–9.18.39, 9.20.0–9.20.13, 9.21.0–9.21.12, 9.11.3-S1–9.16.50-S1, 9.18.11-S1–9.18.39-S1, and 9.20.9-S1–9.20.13-S1. Successful exploitation allows remote unauthenticated attackers to manipulate cached DNS data and redirect subsequent resolution.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Forged DNS records can compromise the integrity of answers returned to clients sharing the poisoned resolver cache. Malicious nameserver or glue records can redirect resolution for a zone apex or sibling domains to attacker-controlled infrastructure, enabling domain hijacking and traffic redirection. The primary established impact is DNS integrity compromise; code execution, privilege escalation, and direct confidentiality compromise are not established for this vulnerability.
Mitigation
If you can’t patch tonight, do this now.
Restrict recursion to trusted clients and disable recursive service where it is unnecessary. Enable DNSSEC validation where applicable to protect signed DNS data; this does not provide equivalent protection for unsigned zones. Network source-address validation can reduce opportunities for spoofed-response injection but is not a substitute for patching. On affected F5 BIG-IP deployments, disable 'Use BIND Server on BIG-IP' in the DNS profile if BIND is unnecessary, or configure BIND with recursion set to 'no'. Disabling BIND can affect configurations that use it as a fallback.
Remediation
Patch, then assume compromise.
Upgrade to a supported BIND release containing the fix or install the operating-system vendor's backported security updates. Recommended patched releases include BIND 9.18.41 or later, 9.20.15 or later, 9.21.14 or later, and Supported Preview Edition 9.18.41-S1 or 9.20.15-S1, as applicable. Migrate unsupported branches to a supported fixed branch. For vendor-bundled BIND components, apply the corresponding product update rather than relying solely on the upstream version number.
Exploits
2 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.
References
Frequently asked questions
- Is CVE-2025-40778 exploited in the wild?
- As of Nov 14, 2026, Mallory has no reports of CVE-2025-40778 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2025-40778?
- Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2025-40778, the earliest disclosed Oct 29, 2025.
- Is there a patch for CVE-2025-40778?
- Upgrade to a supported BIND release containing the fix or install the operating-system vendor's backported security updates. Recommended patched releases include BIND 9.18.41 or later, 9.20.15 or later, 9.21.14 or later, and Supported Preview Edition 9.18.41-S1 or 9.20.15-S1, as applicable.
- How severe is CVE-2025-40778?
- CVE-2025-40778 has a CVSS v3.1 score of 8.6 (High) and an EPSS score of 0.77% (56th percentile) as of Nov 14, 2026.
Recent activity
79 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.