CVE-2025-8677: ISC BIND 9 · Asymmetric Resource Consumption
Affects ISC BIND 9Source CVE Database V5
Not known to be exploited · 10% EPSS · CVSS 7.5 High.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 10.7% chance of exploitation in 30 days – higher than 95% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 22 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ISC BIND 9 | Affected
| Fixed in– |
AI-suggested
- Monitor ISC and trusted security advisories closely for official patches addressing CVE-2025-8677 and apply them promptly once released.
- Until patches are available, implement rate limiting and query filtering on DNS servers to restrict queries for DNSKEY records or from suspicious sources to reduce exposure to malformed queries.
- Deploy network-level protections such as firewalls and intrusion prevention systems (IPS) to detect and block anomalous DNS traffic patterns indicative of exploitation attempts.
- Consider isolating DNS servers from direct internet exposure where possible, using DNS forwarders or recursive resolvers behind protective layers.
- Review DNSSEC configurations and zone data for correctness to minimize the risk of malformed records triggering the vulnerability internally.
- Conduct regular performance monitoring and alerting on DNS server CPU usage to detect early signs of exploitation or resource exhaustion.
- Engage with DNS infrastructure providers and peers to share threat intelligence and coordinate defensive measures.
- Prepare incident response plans specifically for DNS service disruptions to ensure rapid recovery and communication in case of an attack.
Description
Querying for records within a specially crafted zone containing certain malformed DNSKEY records can lead to CPU exhaustion. This issue affects BIND 9 versions 9.18.0 through 9.18.39, 9.20.0 through 9.20.13, 9.21.0 through 9.21.12, 9.18.11-S1 through 9.18.39-S1, and 9.20.9-S1 through 9.20.13-S1.