CVE-2025-8677: Resource exhaustion via malformed DNSKEY handling in BIND 9
- Vendor
- F5
CVE-2025-8677 is a resource-exhaustion vulnerability in BIND 9 DNSSEC validation. Malformed ECDSA DNSKEY records containing invalid elliptic-curve points cause expensive cryptographic processing and repeated error logging. The signing-key selection logic in select_signing_key() continues checking keys after encountering a malformed matching key, bypassing validation failure-counting protections. Resolving records in an attacker-controlled zone can consequently exhaust CPU resources and deny DNS service. Affected versions are 9.18.0–9.18.39, 9.20.0–9.20.13, 9.21.0–9.21.12, 9.18.11-S1–9.18.39-S1, and 9.20.9-S1–9.20.13-S1. Authoritative-only servers are not affected.
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.
Remote exploitation can saturate resolver CPU resources and amplify error logging, causing delayed or failed DNS lookups for legitimate clients. Testing also demonstrated packet loss and resolver crashes. The vulnerability affects availability; no confidentiality or integrity impact is established.
Mitigation
If you can’t patch tonight, do this now.
No general workaround preserves the affected recursive DNSSEC-validation functionality. Restrict recursion to trusted clients to reduce exposure, although this does not prevent exploitation if permitted clients trigger resolution of a malicious zone. Where recursive service is unnecessary, disable recursion. On affected F5 BIG-IP deployments, disable Use BIND Server if BIND is not required, or configure recursion to 'no'; disabling BIND can disrupt configurations that depend on it as a fallback. Monitor abnormal CPU consumption and DNSSEC error-log volume while arranging updates.
Remediation
Patch, then assume compromise.
Upgrade to a supported BIND release containing the fix. Recommended patched releases include 9.18.41, 9.20.15, 9.21.14, 9.18.41-S1, and 9.20.15-S1; prefer the latest supported maintenance release, since subsequent releases also correct a DNSSEC unsupported-algorithm regression introduced by the fix. For distribution packages or appliances, install the applicable vendor security update, which may backport the fix without changing the upstream version. Update and redeploy affected container images and rebuild dependent images where applicable.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2025-8677 exploited in the wild?
- As of Nov 11, 2026, Mallory has no reports of CVE-2025-8677 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2025-8677?
- As of Nov 11, 2026, Mallory has found no public exploit for CVE-2025-8677.
- Is there a patch for CVE-2025-8677?
- Upgrade to a supported BIND release containing the fix. Recommended patched releases include 9.18.41, 9.20.15, 9.21.14, 9.18.41-S1, and 9.20.15-S1; prefer the latest supported maintenance release, since subsequent releases also correct a DNSSEC unsupported-algorithm regression introduced by the fix.
- What products are affected by CVE-2025-8677?
- F5 Traffix Sdc.
- How severe is CVE-2025-8677?
- CVE-2025-8677 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 11.3% (96th percentile) as of Nov 11, 2026.
Recent activity
43 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.