A BIND recursive resolver may experience excessive resource consumption if it encounters large numbers of a particular kind of invalid DNSSEC record. Default limits on "max-records-per-type" and "max-types-per-name" help mitigate the exposure. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alpine Linux | — | Upgrade bind | Sep 28, 2026 | Sep 16, 2026 |
| Amazon_linux_2023 | — | Upgrade bind-dnssec-utilsUpgrade bind-utilsUpgrade bind-develUpgrade bind-chrootUpgrade bind-debuginfoUpgrade bind-utils-debuginfoUpgrade bind-libsUpgrade bindUpgrade bind-licenseUpgrade bind-docUpgrade bind-libs-debuginfoUpgrade bind-debugsourceUpgrade bind-dnssec-utils-debuginfo | Oct 28, 2026 | Sep 16, 2026 |
| Debian | — | Upgrade bind9 | Sep 21, 2026 | Sep 16, 2026 |
| Freebsd | — | Upgrade bind920 | Oct 5, 2026 | Oct 4, 2026 |
| Ibm Aix | — | Apply the fix or workaround for bind_advisory32 | Nov 2, 2026 | Nov 2, 2026 |
| Redhat_linux | — | No solution exists | Sep 21, 2026 | Sep 16, 2026 |
| Ubuntu | — | Upgrade bind9 (Ubuntu Pro)Upgrade bind9 | Oct 15, 2026 | Oct 14, 2026 |
| Vmware Photon_os | — | Use 'tdnf update' to upgrade all packages to the latest version. | Oct 13, 2026 | Sep 16, 2026 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub