BIND 9 Resolver Crash and Stale CNAME Refresh Flaws Tied to `stale-answer-client-timeout 0`
Patch & Detection Intelligence · 3 sources · Updated 4mo ago · First seen Sep 2, 2025

ISC disclosed CVE-2025-40777, a high-severity denial-of-service flaw in BIND 9 that can cause named to exit during recursive lookups when the resolver is configured as a caching resolver with serve-stale enabled and stale-answer-client-timeout 0. The bug is triggered by a specific CNAME resolution path involving stale cache behavior and can be exploited remotely against affected resolvers; authoritative-only deployments are not believed to be impacted. ISC assigned the issue CVSS 7.5 and CWE-617, said there was no known active exploitation, and identified affected releases as BIND 9.20.0 through 9.20.10, 9.21.0 through 9.21.9, and Supported Preview Edition builds.
Related BIND bug reports show the same configuration also caused stale RRsets in CNAME chains to be mishandled, with refresh queries missing or incomplete and logs incorrectly reporting stale-answer activity for records that were not yet stale. ISC said fixes and regression tests were prepared through its coordinated release process, with the vulnerability addressed in 9.20.11 and 9.21.10 and the stale-refresh bug later fixed in 9.20.12 and 9.21.11. As a workaround, ISC advised operators to upgrade or disable the vulnerable stale-answer settings until patched versions are deployed.


