# CVE-2026-97313: Specific RPZ configurations and query patterns may result in an unexpected exit


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** ALPINE-CVE-2026-97313, AZL-111515, BELL-CVE-2026-97313, DEBIAN-CVE-2026-97313, ECHO-e208-e869-5e59, GHSA-9p2q-wv22-f9q8, MINI-p32m-8cg5-ph4m, UBUNTU-CVE-2026-97313

## What is CVE-2026-97313?

CVE-2026-97313 is a high-severity vulnerability in ISC BIND 9, published on 21 Oct 2026. 

### Official description

A recursive BIND server that receives a query with recursion desired (RD=1) followed by a non-recursive query (RD=0) may exit with an assertion failure, resulting in a denial of service. To be vulnerable, the BIND server must allow recursive queries and have at least two RPZ zones configured: one with the default setting of "recursive-only yes", and the other with "recursive-only no".
This issue affects BIND 9 versions 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.

Weakness: CWE-617 (Reachable Assertion)

## Which versions are affected by CVE-2026-97313?


## How do I fix CVE-2026-97313?

Upgrade to a fixed version.

## Is CVE-2026-97313 being exploited?

There is no known exploitation of CVE-2026-97313 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97313 and fix it if it is affected.

What it is: CVE-2026-97313 is a high-severity vulnerability in ISC BIND 9, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-97313 in the wild and no public exploit code.

Affected product: ISC BIND 9. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-97313/ (Markdown: https://insights.sbomify.com/CVE-2026-97313/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-97313
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-97313
- OSV: https://osv.dev/vulnerability/CVE-2026-97313

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-97313/
Summaries are generated and may contain mistakes; the official description above is the record.