ISC publishes BIND 9.20.31 and 9.21.28 as DNS patching goes monthly
Two new maintenance builds land for the Internet's most widely used DNS server, riding ISC's new release cycle of regular security fixes.
ISC shipped two new maintenance releases of BIND 9 on 18 November 2026. BIND 9.20.31 is the newest point release on the stable branch, which is also the Extended Support Version, while 9.21.28 tops the experimental development line. Both came out at about 09:29 UTC, each bundled with a full source tarball, a PGP signature, and its own release notes. ISC said binary packages and container images would arrive "later today."
Routine on paper. In practice, BIND 9 is a piece of software that dates to the turn of the millennium and is now run out of ISC under Ondřej Surý, who has pushed more than 200 incremental releases since 2017. The interesting part is when these landed, not that they exist. BIND has moved into a monthly security-fix cycle, and these builds ride right on top of the last few months' worth of patches.
A flood of findings, some AI-generated
The reason ISC gives for the faster release cycle is honestly a bit alarming. Back in May 2026 the organization warned that users should expect security fixes in every monthly release, and it pointed the finger at what it called an "unprecedented flood of vulnerability reports." Much of the surge, ISC says, traces back to large language model analysis of open source code.
The uncomfortable half is that those same tools speed up both sides. Researchers find flaws in hours. Attackers probe them just as fast. Both groups are feeding the flood, ISC notes.
The 2026 tally makes the case for the monthly model. One flaw in January, four in March, six in May, roughly nine or ten in July, and 14 in September, the biggest batch of the year. Every release since has folded in its own findings plus any CVEs that leaked through earlier, so the numbers keep stacking up.
The 9.18 deadline you still can't ignore
The migration message is unmistakable. BIND 9.18, the stable branch that preceded 9.20, hit end-of-life in June 2026 with its final release, 9.18.50. ISC's stance is blunt: the risk of unexpected breakage from upgrading is "much lower" than the risk of running an unmaintained version, and EOL builds "should be assumed to be vulnerable to new CVEs." That makes 9.20.31 the obvious target for anyone who hasn't moved yet.
The security picture itself is why November matters. The September batch alone fixed fourteen flaws, landing in 9.20.29 and 9.21.26. The headline was CVE-2026-77692, a DNS-over-HTTPS crash where a single crafted request carrying a cryptographically invalid SIG(0) signature, followed by dropping the connection, would take named down with no authentication needed. The rest covered resource exhaustion, cache poisoning, and integrity gaps on secondary servers. ISC claims it hasn't spotted any of the fourteen exploited in the wild, and none showed up in CISA's known exploited vulnerabilities list.
Keep in mind two things before you upgrade. First, the mirrored release notes still top out at 9.20.30 as this went to press, and ISC's own changelog entries for 9.20.31 and 9.21.28 hadn't fully landed yet. The official announcement gives no itemized list, so treat any claim about exactly what these two fixed as provisional. Second, stick with 9.20.31 for production. The 9.21 development branch is experimental, its vulnerabilities get fixed as ordinary bugs without separate CVE advisories, and minor releases can break compatibility.
When it comes to performance, ISC's own resolver benchmarks claim up to six times less memory on TCP-only traffic and better cold-cache latency, though self-reported performance numbers always warrant a grain of salt.
Head here to ISC's main download hub.
