CVE-2026-10822

The record

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 packages

Related vulnerabilities

• CVE-2026-105754 vLLM is an inference and serving engine for large language models. CWE-617
• CVE-2026-105753 vLLM is an inference and serving engine for large language models. CWE-617
• CVE-2026-98151 In the Linux kernel, the following vulnerability has been resolved: bpf: Fix REG… CWE-617
• CVE-2026-84450 libheif is a HEIF and AVIF file format decoder and encoder. CWE-617
• CVE-2026-8674 Initializing the DNS stub resolver from an /etc/resolv.conf file, or a LOCALDOMAIN… CWE-617
• CVE-2026-80274 If a BIND resolver sends a query for a DNSSEC-signed authoritative zone, and the… CWE-617
• CVE-2026-76163 If BIND is loaded with a "`named.conf`" file that contains no global "`options`" block… CWE-617
• CVE-2026-86317 A vulnerability was detected in ggml-org llama.cpp up to 0.4.0. CWE-617