If a named caching resolver is configured with serve-stale-enable yes, and with stale-answer-client-timeout set to 0
Source GCVE Database
Not known to be exploited · CVSS 7.5 High.
Data as of 4 Nov 2026, 17:54 UTC
Thin evidence
One scorer or none| CNA (isc) | CVSS 3.1 | 7.5 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 16 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.
What to do
AI-suggested
Until a fix is available, consider avoiding the configuration of stale-answer-client-timeout set to 0 with serve-stale-enable yes, or monitor for vendor updates.
Description
A vulnerability in BIND 9 caching resolver versions 9.20.0 through 9.20.10, 9.21.0 through 9.21.9, and 9.20.9-S1 through 9.20.10-S1 allows the daemon to abort with an assertion failure when configured with serve-stale-enable yes and stale-answer-client-timeout set to 0, triggered by specific CNAME chain conditions.