Skip to main content
Mallory
HighVulnerability

CVE-2026-96888: BIND 9 Redirect Processing Assertion Failure with Strict QNAME Minimization

Published Oct 21, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days67 mentions · peak 11 in a dayToday
CVSS7.5High · v3.1
EPSS0.46%41st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Internet Systems Consortium
IdentifiersCVE-2026-96888CWE-617 · Reachable Assertion

CVE-2026-96888 is a denial-of-service vulnerability in ISC BIND 9 resolvers configured with both a redirect zone and strict QNAME minimization. Processing a redirect under this configuration can trigger an assertion failure and terminate the resolver. Affected versions are 9.16.0 through 9.18.50, 9.20.0 through 9.20.29, 9.21.0 through 9.21.26, 9.16.8-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.29-S1.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

An assertion failure can terminate the BIND resolver, interrupting DNS resolution for dependent clients. Repeated triggering could cause recurring service disruption after restarts. No confidentiality or integrity impact is established for this vulnerability.

Mitigation

If you can’t patch tonight, do this now.

As a configuration-based workaround, avoid using a redirect zone together with "qname-minimization strict" on affected resolvers. Remove the redirect-zone configuration or change strict QNAME minimization to a supported non-strict setting, accounting for operational and privacy requirements. This workaround is inferred from the triggering conditions rather than explicitly confirmed as vendor guidance.

Remediation

Patch, then assume compromise.

Install the vendor-provided BIND security update for the applicable operating system and release stream. Fixed upstream releases identified include BIND 9.20.30, 9.21.27, and Supported Preview Edition 9.20.30-S1. Fedora also provides corrected BIND 9.18.51-based packages. Distribution-maintained packages may contain backported fixes without adopting these upstream version numbers; verify remediation against the applicable vendor advisory.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
Internet Systems ConsortiumBindapplication
FAQ

Frequently asked questions

Is CVE-2026-96888 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-96888 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-96888?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-96888.
Is there a patch for CVE-2026-96888?
Install the vendor-provided BIND security update for the applicable operating system and release stream. Fixed upstream releases identified include BIND 9.20.30, 9.21.27, and Supported Preview Edition 9.20.30-S1.
What products are affected by CVE-2026-96888?
Internet Systems Consortium Bind.
How severe is CVE-2026-96888?
CVE-2026-96888 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.46% (41st percentile) as of Nov 17, 2026.
Activity feed

Recent activity

67 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+53 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.