CVE-2025-40780: DNS Cache Poisoning via Predictable PRNG in ISC BIND 9
CVE-2025-40780 is a remote DNS cache-poisoning vulnerability in ISC BIND 9 operating as a recursive resolver or forwarder. BIND uses the xoshiro128** pseudorandom number generator for outbound DNS transaction IDs, UDP source ports, and RRset shuffling. Under exploitable circumstances, observable outputs allow attackers to predict subsequent query parameters, undermining the entropy used to distinguish legitimate DNS responses from forged ones. Spoofed responses matching those parameters can be accepted and cached. Affected versions are 9.16.0–9.16.50, 9.18.0–9.18.39, 9.20.0–9.20.13, 9.21.0–9.21.12, 9.16.8-S1–9.16.50-S1, 9.18.11-S1–9.18.39-S1, and 9.20.9-S1–9.20.13-S1. Authoritative-only deployments are not affected by this resolver cache-poisoning issue.
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.
Successful exploitation compromises DNS resolution integrity by inserting attacker-selected records into the resolver cache. Subsequent clients querying affected records can receive forged answers and be redirected to attacker-controlled systems, potentially facilitating phishing, credential theft, malware distribution, interception attempts, or censorship. These downstream outcomes depend on application-layer protections and the records poisoned; the vulnerability does not itself establish arbitrary code execution or privilege escalation.
Mitigation
If you can’t patch tonight, do this now.
No general BIND configuration workaround is identified as a substitute for patching. Restrict recursion to trusted clients to reduce exposure, but do not treat access restrictions as correcting the PRNG weakness. DNS Cookies are not a reliable standalone mitigation because some attack scenarios remain possible with cookies enabled. On affected F5 BIG-IP DNS systems, disable the 'Use BIND Server on BIG-IP' option in the applicable DNS profile where operationally feasible; this can affect configurations relying on BIND fallback.
Remediation
Patch, then assume compromise.
Upgrade to BIND 9.18.41, 9.20.15, 9.21.14, or a later supported fixed release. Supported Preview Edition users should install 9.18.41-S1, 9.20.15-S1, or a later applicable fixed release. The fix replaces the affected generator with a cryptographically secure PRNG. Migrate discontinued branches, including 9.16, to a supported fixed branch. For distribution-packaged or appliance-integrated BIND, install the vendor's security update containing the fix; affected F5 BIG-IP DNS deployments require a vendor-designated fixed release.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Frequently asked questions
- Is CVE-2025-40780 exploited in the wild?
- As of Nov 4, 2026, Mallory has no reports of CVE-2025-40780 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2025-40780?
- As of Nov 4, 2026, Mallory has found no public exploit for CVE-2025-40780.
- Is there a patch for CVE-2025-40780?
- Upgrade to BIND 9.18.41, 9.20.15, 9.21.14, or a later supported fixed release. Supported Preview Edition users should install 9.18.41-S1, 9.20.15-S1, or a later applicable fixed release.
- How severe is CVE-2025-40780?
- CVE-2025-40780 has a CVSS v3.1 score of 8.6 (High) and an EPSS score of 0.47% (41st percentile) as of Nov 4, 2026.
Recent activity
40 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.