BIND DNS vulnerabilities and fixes

CVEs that mention BIND DNS, ranked by priority. 5 tracked.

BIND DNS has 5 tracked vulnerabilities, 0 critical and 1 exploited in the wild (CISA KEV). A fixed release or vendor patch exists for 5. Most recent: 2026-10-21. Highest priority: CVE-2015-5477 (score 91/100).

• CVE-2015-5477 HIGH 7.5 EXPLOITED UPGRADE MITIGATE ISC BIND Data Processing Errors Vulnerability
• CVE-2026-94300 HIGH 8.1 Replaying GSS-TSIG signed UDP messages can result in memory corruption in "`named`"
• CVE-2026-19630 HIGH 7.5 In a BIND resolver, inbound DNS protocol messages with a particular structure will result in additional proces
• CVE-2026-96888 HIGH 7.5 A BIND resolver that is configured with both a "redirect" zone and "qname-minimization strict" may abort with
• CVE-2026-97313 HIGH 7.5 A recursive BIND server that receives a query with recursion desired (RD=1) followed by a non-recursive query

FAQ

How do I fix BIND DNS vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is BIND DNS being exploited right now?

Yes: 1 BIND DNS CVE is on the CISA Known Exploited Vulnerabilities list, so patch it first.

Which BIND DNS CVE should I patch first?

CVE-2015-5477 currently ranks highest (91/100): ISC BIND Data Processing Errors Vulnerability.

← Back to latest CVEs