Live › vulnerability › CVE-2026-97313
Go to dashboardA recursive BIND 9 resolver that receives a query with recursion desired followed by a non-recursive query can exit on an assertion failure. The result is a denial of service that takes the resolver offline.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Only recursive BIND resolvers that have at least two RPZ zones configured with different recursive-only settings are exposed. Authoritative-only servers and resolvers without RPZ can skip this one.
No product ranges from the sources yet.
named -v or named -V to read the installed BIND version and compare it to the affected ranges.recursion yes or default recursion together with at least two response-policy zones, one with recursive-only yes and one with recursive-only no.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-97313")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.