Skip to main content
Mallory
← Back to News
widely-deployed-product-advisoryinternet-facing-service-vulnerabilityoperational-disruption

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

BIND 9 Resolver Crash and Stale CNAME Refresh Flaws Tied to `stale-answer-client-timeout 0`

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.

Patch this, or something else?See real exploitation activity before you spend the cycle.
Triage this advisory
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

4 events · Jul 16, 2025 – Sep 2, 2025
  1. Sep 2, 20251y ago

    ISC issue tracks CVE-2025-40777 fixes and regression tests

    An ISC GitLab issue for CVE-2025-40777 recorded that fixes and regression tests had been prepared and merged as part of ISC's coordinated release process. The issue described a reproducible crash path involving `zemanta-nychi2.outbrain.org`, low-TTL data, and stale-answer refresh logic.

    [CVE-2025-40777] A possible assertion failure when using the 'stale-answer-client-timeout 0' option (#5372) · Issue · isc-projects/bind9
  2. Jul 24, 20251y ago

    ISC publishes advisory with affected versions and fixes

    ISC published a knowledge base advisory for CVE-2025-40777 listing affected BIND 9.20.0-9.20.10 and 9.21.0-9.21.9 versions, stating authoritative services were believed unaffected. The advisory recommended upgrading to BIND 9.20.11 or 9.21.10 or disabling the vulnerable stale-answer settings as a workaround.

    CVE-2025-40777: A possible assertion failure when using the 'stale-answer-client-timeout 0' option
  3. Jul 23, 20251y ago

    Bug report documents stale CNAME refresh issue in BIND

    An ISC GitLab issue documented a bug where stale RRsets in a CNAME chain were not always refreshed correctly when `stale-answer-client-timeout` was set to 0. The report also noted misleading stale-answer log messages and identified BIND 9.18.33 and the bind-9.18 branch as affected.

    Stale RRsets in a CNAME chain aren't refreshed when stale-answer-client-timeout is 0 (#5243) · Issue · isc-projects/bind9
  4. Jul 16, 20251y ago

    ISC publicly discloses CVE-2025-40777

    ISC publicly disclosed CVE-2025-40777, a high-severity denial-of-service flaw in BIND resolvers tied to the use of `stale-answer-client-timeout 0`. The issue can cause `named` to crash during recursive lookups involving stale cache behavior.

    [CVE-2025-40777] A possible assertion failure when using the 'stale-answer-client-timeout 0' option (#5372) · Issue · isc-projects/bind9
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

2 linked
Bind 9Bind
Do you run this?See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
Prioritize This Patch
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.