If BIND encounters a particular invalid data structure in a DNS record, it will accept the invalid data, and may subsequently abort and exit.
BIND will first need to store a DNS record for a key (KEY, DNSKEY, etc.). That key must specify a PRIVATEDNS algorithm (253), and in the algorithm identifier, improperly give a length longer than the actual identifier data. The invalid identifier will be stored. If BIND later needs to render that record to text, it will use the invalid length during processing, leading to a consistency check failing. This issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.18.11-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.
CVSS Details
- CVSS 3.1 Base Score: 6.5
- CVSS 3.1 Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H)
Covered by Rapid7
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alpine Linux | — | Upgrade bind | Jul 28, 2026 | Jul 22, 2026 |
| Amazon_linux_2023 | — | Upgrade bind-docUpgrade bind-licenseUpgrade bind-dnssec-utils-debuginfoUpgrade bind-libs-debuginfoUpgrade bind-utils-debuginfoUpgrade bindUpgrade bind-libsUpgrade bind-develUpgrade bind-debugsourceUpgrade bind-debuginfoUpgrade bind-chrootUpgrade bind-dnssec-utilsUpgrade bind-utils | Aug 10, 2026 | Jul 22, 2026 |
| Debian | — | Upgrade bind9 | Jul 28, 2026 | Jul 28, 2026 |
| F5 Big Ip | — | Update F5 BIG-IP to the latest version | Sep 9, 2026 | Sep 8, 2026 |
| Ibm Aix | — | Apply the fix or workaround for bind_advisory31 | Sep 16, 2026 | Sep 16, 2026 |
| Redhat_linux | — | No solution exists | Jul 24, 2026 | Jul 22, 2026 |
| Ubuntu | — | Upgrade bind9 | Aug 19, 2026 | Aug 19, 2026 |
Prioritise with Active Threat Intelligence
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