Skip to main content
Mallory
HighVulnerability

CVE-2026-97313: Denial of Service in BIND 9 RPZ Query Processing

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

CVE-2026-97313 is a reachable assertion vulnerability in BIND 9 Response Policy Zone (RPZ) query processing. A recursive server receiving a query with recursion desired (RD=1), followed by a non-recursive query (RD=0), may terminate with an assertion failure when resuming an RPZ-initiated query. Exploitation requires recursion to be enabled and at least two RPZ zones configured: one with recursive-only yes, the default, and another with recursive-only no. 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.11.3-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.

Successful exploitation terminates the BIND DNS server process, interrupting DNS resolution and any other DNS services provided by that process until service is restored. This vulnerability establishes an availability impact; arbitrary code execution, confidentiality loss, and integrity compromise are not established.

Mitigation

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

Where operationally feasible, disable recursion or eliminate the mixed RPZ recursive-only configuration so that zones with recursive-only yes and recursive-only no are not configured together. Restrict recursive-query access to trusted clients to reduce exposure, although permitted clients can still reach the vulnerable processing. These measures follow from the exploitation prerequisites; no vendor-approved temporary workaround is established.

Remediation

Patch, then assume compromise.

Install a vendor security update explicitly addressing CVE-2026-97313. Fixed releases include BIND 9.20.30, 9.21.27, and Supported Preview Edition 9.20.30-S1, or later fixed releases within the corresponding branches. Fedora also provides corrected BIND 9.18.51-based packages. For distribution-managed installations, use the applicable vendor security packages, which may backport the fix without adopting these upstream version numbers.

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-97313 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-97313 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-97313?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-97313.
Is there a patch for CVE-2026-97313?
Install a vendor security update explicitly addressing CVE-2026-97313. Fixed releases include BIND 9.20.30, 9.21.27, and Supported Preview Edition 9.20.30-S1, or later fixed releases within the corresponding branches.
What products are affected by CVE-2026-97313?
Internet Systems Consortium Bind.
How severe is CVE-2026-97313?
CVE-2026-97313 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.45% (39th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

65 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 activity3Community discussion across Reddit, Mastodon, and other social sources.