CVE-2026-97313

Specific RPZ configurations and query patterns may result in an unexpected exit

  • High 7.5

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.

Key facts

Published
21 Oct 2026
Last changed
21 Oct 2026
Assigned by
isc
EPSS
0.448% likely to be exploited in the next 30 days, higher than 39.487% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: yes; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.5CVSS 3.1, Highfrom the CNA (isc)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
ISCBIND 9
  • Default status: unaffected
  • 9.16.0 up to and including 9.18.50 (affected)
  • 9.20.0 up to and including 9.20.29 (affected)
  • 9.21.0 up to and including 9.21.26 (affected)
  • 9.11.3-S1 up to and including 9.18.50-S1 (affected)
  • 9.20.9-S1 up to and including 9.20.29-S1 (affected)

Timeline

  1. 21 Oct 2026 Published

Weakness

References