CVSS base score: 7.5 (High) vendor CNA · v3.1
Score assigned by the vendor's own CVE Numbering Authority (CNA); CISA's Vulnrichment program adds a score only when the CNA omits one.
Vendor: ISC Product: BIND 9
To keep its cache database efficient, `named` running as a recursive resolver occasionally attempts to clean up the database. It uses several methods, including some that are asynchronous: a small chunk of memory pointing to the cache element that can be cleaned up is first allocated and then queued for later processing. It was discovered that if the resolver is continuously processing query patterns triggering this type of cache-database maintenance, `named` may not be able to handle the cleanup events in a timely manner. This in turn enables the list of queued cleanup events to grow infinitely large over time, allowing the configured `max-cache-size` limit to be significantly exceeded. This issue affects BIND 9 versions 9.16.0 through 9.16.45 and 9.16.8-S1 through 9.16.45-S1.
Each milestone comes from a different source, so gaps between them are gaps in what those sources publish, not evidence that nothing happened. EPSS history for this CVE holds 148 points from 2024-02-17, tracked daily from 2026-09-09; earlier points are weekly, which dates a spike to within a week. Peak probability 2.5% on 2025-03-29.
Check whether a specific version is affected →
What each source publishes about which product versions carry this vulnerability, kept as written rather than merged. Absence here means no source has published applicability data, not that nothing is affected.
No mentions found in monitored research blogs or news feeds.
Coverage across public collections only: Nuclei and OpenVAS NVT (scan);
Snort and Suricata ET Open (network); Sigma and YARA (host/SIEM);
Metasploit, Exploit-DB and public GitHub repositories (exploit). Absence
here means nothing public was found, not that detection is impossible.
GitHub PoC repositories are collected automatically by
PoC-in-GitHub (CC0) and are not vetted:
some are fakes and some are malware. Treat them as evidence that code was
published, not as code to run.
OpenVAS coverage derives from the Greenbone Community Feed, made available
under the Open Database License (ODbL) v1.0;
its individual Vulnerability Tests are licensed
GNU GPL v2.
Where the distribution has shipped a fix, and in which version. Green means the release has resolved it, amber that it is still open. Data from the Debian Security Tracker, used under Debian's MIT / GPLv2+ terms. Debian is upstream of several other distributions, so a fix here often precedes theirs.
Defensive techniques inferred by MITRE D3FEND from the underlying weakness (CWE-789) — general hardening and detection guidance for this weakness class, not a vendor patch for this specific CVE.
| Source | Date | Record |
|---|---|---|
| CISA Vulnrichment | 2024-06-28 | source record → |
| Date | Advisory | Issuer |
|---|---|---|
| 2024-02-13 | ISC Releases Security Advisories for BIND 9 | CISA |
No exploit-tool sightings recorded for this CVE.
Evidence tiers are explained on the About page — a merged Metasploit module is far stronger evidence than a distro package mention.
CVE.org record → NVD entry → FortiGuard Labs → Rapid7 AttackerKB →