Under certain circumstances, BIND is too lenient when accepting records from answers, allowing an attacker to inject forged data into the cache. This issue affects BIND 9 versions 9.11.0 through 9.16.50, 9.18.0 through 9.18.39, 9.20.0 through 9.20.13, 9.21.0 through 9.21.12, 9.11.3-S1 through 9.16.50-S1, 9.18.11-S1 through 9.18.39-S1, and 9.20.9-S1 through 9.20.13-S1.
Fix
Public exploits 3
- nehkark/CVE-2025-40778 PoC on GitHub
- nicholasC03/DNS-Poisoning-Triage-Lab PoC on GitHub
- sirbuvladste/BIND-9-Cache-Poisoning-PoC---CVE-2025-40778 PoC on GitHub
Each line links to the index that lists it, never to exploit code. Exploit-DB's "verified" and a Metasploit rank of good or better count as verified; a PoC-in-GitHub entry is a repository's claim.
Vendor advisories in the News 1
- USN-8929-1: Bind vulnerabilities Ubuntu Security Notices · 2026-10-14
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 8.6NVD modified 2026-10-08 11:10
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.