Bind 9 9.21 (Development) End of Life Date
Bind 9 9.21 (Development) end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
Bind 9 9.21 was released on August 13, 2024 and has no published end-of-life date yet. It is not an LTS release; Bind 9 reserves longer patch windows for its LTS versions. Its most recent patch is 9.21.25, published August 5, 2026.
| Version | Latest | EOL Date | Status |
|---|---|---|---|
| 9.16 LTS | 9.16.50 | Mar 31, 2024 | EOL |
| 9.18 (ESV) LTS | 9.18.50 | Jun 30, 2026 | EOL |
| 9.20 (Stable) LTS | 9.20.27 | Jul 8, 2028 | Active |
| → 9.21 (Development) | 9.21.25 | EOL | Active |
What does Bind 9 9.21 (Development) end of life mean?
When Bind 9 9.21 (Development) reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Bind 9 9.21 (Development) past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Bind 9 9.21 (Development) or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.