CVE-2026-19668: ISC BIND 9 · Inefficient Algorithmic Complexity
Affects ISC BIND 9Source CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 31 Oct 2026, 08:20 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% 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:LExploitation evidence
Disclosed: evidence found.
CVE published 16 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ISCBIND 9 | Affected
| Fixed in– |
GitHubisc/bind9pkg:github/isc/bind9Other threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Default limits on "max-records-per-type" and "max-types-per-name" provide some mitigation.
Description
CVE-2026-19668 is a vulnerability in ISC BIND 9 recursive resolver where processing large numbers of certain invalid DNSSEC records can cause excessive resource consumption. Default limits on "max-records-per-type" and "max-types-per-name" provide some mitigation. This affects multiple BIND 9 versions from 9.11.0 through 9.21.25 and their respective S1 variants.