CVE-2026-12617: BIND 9 resolver denial of service through CNAME/DNAME response ordering
- Vendor
- Internet Systems Consortium
CVE-2026-12617 is a reachable assertion vulnerability in the BIND 9 resolver that causes the named process to terminate when particular CNAME or DNAME responses arrive after related positive A-record responses. One trigger involves a DNAME query and an A query for a name below that DNAME: the authoritative server returns a positive A response, delays the DNAME response, and then returns a negative DNAME response. Another involves CNAME and A queries for the same name: a positive A response arrives first, followed by a delayed, self-referential CNAME response. These conditions can trigger an assertion failure and interrupt DNS service. Affected versions are BIND 9.18.0–9.18.50, 9.20.0–9.20.24, Supported Preview Edition 9.18.11-S1–9.18.50-S1, and 9.20.9-S1–9.20.24-S1.
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.
A remote, unauthenticated attacker can cause the resolver process to exit unexpectedly, denying DNS resolution to clients served by that process. The vulnerability affects availability; no confidentiality or integrity impact is identified. Its CVSS v3.1 base score is 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
Mitigation
If you can’t patch tonight, do this now.
ISC identifies no known workaround for this vulnerability. Restricting recursive DNS access to trusted clients can reduce exposure but does not eliminate malicious upstream-response risk. For affected F5 BIG-IP DNS deployments, disable the BIND server in the applicable DNS profile, disable recursion where unnecessary, or restrict recursion using an allow-recursion ACL permitting only authorized internal clients.
Remediation
Patch, then assume compromise.
Upgrade to a vendor-supported BIND release or distribution package explicitly containing the fix, then restart named. ISC released BIND 9.20.26 and 9.21.24 with fixes and recommends selecting the appropriate patched release for the deployment. Distribution backports include Debian trixie bind9 1:9.20.26-1~deb13u1 and Ubuntu bind9 1:9.20.24-1ubuntu0.2 for 26.04 LTS, 1:9.18.39-0ubuntu0.24.04.6 for 24.04 LTS, and 1:9.18.39-0ubuntu0.22.04.5 for 22.04 LTS. Backported packages may retain upstream version numbers within the affected ranges. No fixed F5 BIG-IP release is identified; apply an F5 release containing the fix when available.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2026-12617 exploited in the wild?
- As of Nov 3, 2026, Mallory has no reports of CVE-2026-12617 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-12617?
- As of Nov 3, 2026, Mallory has found no public exploit for CVE-2026-12617.
- Is there a patch for CVE-2026-12617?
- Upgrade to a vendor-supported BIND release or distribution package explicitly containing the fix, then restart named. ISC released BIND 9.20.26 and 9.21.24 with fixes and recommends selecting the appropriate patched release for the deployment.
- What products are affected by CVE-2026-12617?
- Internet Systems Consortium Bind.
- How severe is CVE-2026-12617?
- CVE-2026-12617 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.52% (45th percentile) as of Nov 3, 2026.
Recent activity
21 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.