Skip to content
Sign in
6.5 Medium

CVE-2026-10822 If BIND encounters a particular invalid data structure in a DNS record, it will accept the invalid data, and may…

Description

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.

Affected products and versions

Product Affected versions Fixed in
BIND 9 9.21 9.21.0 → 9.21.23 No fix stated
BIND 9 9.20 9.20.0 → 9.20.24 No fix stated
BIND 9 9.18 9.18.0 → 9.18.50 No fix stated

Other CVEs of BIND 9

The 87 CVEs of BIND 9 →
CVE-2026-97313 A recursive BIND server that receives a query with recursion desired (RD=1) followed by a non-recursive query (RD=0) may… 7.5 High CVE-2026-96888 A BIND resolver that is configured with both a "redirect" zone and "qname-minimization strict" may abort with an… 7.5 High CVE-2026-94300 Replaying GSS-TSIG signed UDP messages can result in memory corruption in "`named`" 8.1 High CVE-2026-19630 In a BIND resolver, inbound DNS protocol messages with a particular structure will result in additional processing, with… 7.5 High
Track this CVE