Skip to main content
Mallory
HighVulnerability

CVE-2025-40777: BIND 9 serve-stale resolver assertion failure

Published Jul 16, 2025 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v3.1
EPSS1.0%64th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2025-40777CWE-617 · Reachable Assertion

CVE-2025-40777 is a reachable assertion vulnerability in the BIND 9 named caching resolver's serve-stale processing. During recursive resolution, a specific CNAME chain containing a combination of cached and authoritative records can reach an assertion failure when stale-answer handling is enabled with a zero client timeout. The assertion aborts the named process. Affected releases are BIND 9.20.0 through 9.20.10, 9.21.0 through 9.21.9, and 9.20.9-S1 through 9.20.10-S1.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A remote unauthenticated attacker can cause an affected named caching resolver to abort, producing denial of service for recursive DNS resolution. Confidentiality and integrity impacts are not identified.

Mitigation

If you can’t patch tonight, do this now.

Disable the vulnerable stale-answer configuration by setting stale-answer-client-timeout to disabled/off, or disable stale-answer serving. Restrict recursive service to trusted clients to reduce exposure while patching.

Remediation

Patch, then assume compromise.

Upgrade affected installations to BIND 9.20.11, BIND 9.21.10, or a later supported release containing the vendor fix. Apply the corresponding fixed Supported Preview Edition release where applicable.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2025-40777 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2025-40777 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-40777?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2025-40777.
Is there a patch for CVE-2025-40777?
Upgrade affected installations to BIND 9.20.11, BIND 9.21.10, or a later supported release containing the vendor fix. Apply the corresponding fixed Supported Preview Edition release where applicable.
How severe is CVE-2025-40777?
CVE-2025-40777 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 1.0% (64th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

18 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+1 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity13Community discussion across Reddit, Mastodon, and other social sources.