Skip to main content
Mallory
HighVulnerability

CVE-2025-8677: Resource exhaustion via malformed DNSKEY handling in BIND 9

Published Oct 22, 2025 · Updated 7 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 1 in a dayToday
CVSS7.5High · v3.1
EPSS11.3%96th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
F5
IdentifiersCVE-2025-8677CWE-405 · Asymmetric Resource Consumption…

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.

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.

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.

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.
Exposure surface

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.

VendorProductType
F5Traffix Sdcapplication
FAQ

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.
Activity feed

Recent activity

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

View more in app →
tenable nessus pluginsNews · Nov 3, 2026AlmaLinux 9.2 [TuxCare] Security Update: bind / bind-chroot / ... | Tenable®A CPU-exhaustion denial-of-service vulnerability in BIND 9 triggered by queries involving specially crafted DNS zones containing malformed DNSKEY records. 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. The advisory identifies affected packages on AlmaLinux 9.2 and assigns a CVSS v3 base score of 7.5. Nessus detects exposure using self-reported version information rather than testing exploitation.Read more ↗tenable nessus pluginsNews · Oct 22, 2026AlmaLinux 9.2 [TuxCare] Security Update: bind / bind-chroot / ... | Tenable®A CPU-exhaustion vulnerability in BIND 9 triggered by queries involving specially crafted zones with malformed DNSKEY records. Affected versions include 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. The advisory provides updated packages for AlmaLinux 9.2. Nessus identifies exposure through self-reported version information rather than testing exploitation.Read more ↗tenable nessus pluginsNews · Oct 19, 2026Ubuntu 14.04 LTS / 16.04 LTS / 18.04 LTS / 20.04 LTS / 22.04 L... | Tenable®Listed in Ubuntu BIND 9 security update USN-8929-1. No vulnerability-specific technical details are provided. Exploit availability is stated for the bulletin collectively, without identifying which CVEs have exploits.Read more ↗tenable nessus pluginsNews · Oct 1, 2026AlmaLinux 9.6 [TuxCare] Security Update: bind / bind-chroot / ... | Tenable®A vulnerability tracked as CVE-2025-8677, addressed by an Alma Linux security update. The supplied content provides severity and CVSS metadata but does not describe the affected component or technical flaw.Read more ↗
+13 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 activity17Community discussion across Reddit, Mastodon, and other social sources.