Quick answers
- Is CVE-2026-96888 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-96888 being exploited in the wild.
- How severe is CVE-2026-96888?
- High severity, with a CVSS score of 7.5, published 21 October 2026.
- Which products and versions are affected?
- Isc Bind 9.16.0–9.18.50, 9.20.0–9.20.29, 9.21.0–9.21.26, 9.16.8-S1–9.18.50-S1, 9.20.9-S1–9.20.29-S1.
- Is there a fix for CVE-2026-96888?
- Yes: fixed in BIND 9.18.51, 9.20.30, 9.21.27. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-96888 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-96888?
- Check whether you run Isc Bind at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: BIND 9.18.51, 9.20.30, 9.21.27
Technical details
An assertion failure occurs in BIND resolvers configured with both "redirect" zones and "qname-minimization strict" enabled during redirect processing. The vulnerability affects specific BIND 9 version ranges across stable (9.16.0–9.18.50, 9.20.0–9.20.29, 9.21.0–9.21.26) and ESV (Extended Support Version) branches. A network attacker can trigger this condition through specially crafted DNS queries, resulting in resolver process termination and denial of service.
Affected products
- ISC BIND 9.16.0–9.18.50, 9.20.0–9.20.29, 9.21.0–9.21.26, 9.16.8-S1–9.18.50-S1, 9.20.9-S1–9.20.29-S1
Timeline
- 2026-10-21: disclosed