CVE-2026-10822
published 2026-07-22CVE-2026-10822: 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…
PriorityP334medium6.5CVSS 3.1
AVNACLPRNUIRSUCNINAH
EPSS
0.38%
31.3th percentile
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
8 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| isc | bind | — | — |
| isc | bind_9 | 9.18.0 – 9.18.50 | — |
| isc | bind_9 | 9.18.11-S1 – 9.18.50-S1 | — |
| isc | bind_9 | 9.20.0 – 9.20.24 | — |
| isc | bind_9 | 9.20.9-S1 – 9.20.24-S1 | — |
| isc | bind_9 | 9.21.0 – 9.21.23 | — |
| isc | dhcp | — | — |
| ubuntu | bind9 | — | — |
CVSS provenance
nvdv3.16.5MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
vendor_ubuntu6.8MEDIUM
vendor_redhat6.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Ubuntu
Bind vulnerabilities
vendor_ubuntu·2026-08-19·CVSS 6.8
CVE-2026-11721 [MEDIUM] Bind vulnerabilities
Title: Bind vulnerabilities
Summary: Several security issues were fixed in Bind.
It was discovered that Bind incorrectly accepted NSEC3 records whose signer
name did not match the owning zone. A remote attacker could possibly use
this issue to perform NSEC3 impersonation attacks, bypassing DNSSEC
validation. (CVE-2026-10723)
It was discovered that Bind incorrectly handled Key Records using the
PRIVATEDNS algorithm. A remote attacker could possibly use this issue to
cause Bind to crash, resulting in a denial of service. (CVE-2026-10822)
It was discovered that Bind incorrectly handled wildcard CNAME expansion in
Response Policy Zones. A remote attacker could possibly use this issue to
bypass configured RPZ policies. (CVE-2026-11331)
It was discovered that Bind performed unnecessary vali
Red Hat
bind: bind9: Key Record using PRIVATEDNS algorithm may lead to exit
vendor_redhat·2026-07-22·CVSS 6.5
CVE-2026-10822 [MEDIUM] CWE-617 bind: bind9: Key Record using PRIVATEDNS algorithm may lead to exit
bind: bind9: Key Record using PRIVATEDNS algorithm may lead to exit
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.
If BIND enco
VulDB
ISC BIND 9 up to 9.21.23 Render input validation (WID-SEC-2026-2484)
vuldb·2026-08-15·CVSS 6.5
CVE-2026-10822 [MEDIUM] ISC BIND 9 up to 9.21.23 Render input validation (WID-SEC-2026-2484)
A vulnerability was found in ISC BIND 9 up to 9.18.50/9.18.50-S1/9.20.24/9.20.24-S1/9.21.23. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the component Render. Executing a manipulation can lead to improper input validation.
This vulnerability is registered as CVE-2026-10822. It is possible to launch the attack remotely. No exploit is available.
It is recommended to upgrade the affected component.
GHSA
If BIND encounters a particular invalid data structure in a DNS record, it will accept the invalid data, and may subsequently abort and exit.
ghsa_unreviewed·2026-07-22
CVE-2026-10822 [MEDIUM] CWE-617 If BIND encounters a particular invalid data structure in a DNS record, it will accept the invalid data, and may subsequently abort and exit.
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.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2026-10822 bind: Key Record using PRIVATEDNS algorithm may lead to exit [fedora-all]
bugzilla·2026-09-01·CVSS 6.5
CVE-2026-10822 [MEDIUM] CVE-2026-10822 bind: Key Record using PRIVATEDNS algorithm may lead to exit [fedora-all]
CVE-2026-10822 bind: Key Record using PRIVATEDNS algorithm may lead to exit [fedora-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
A KEY/DNSKEY record with PRIVATEDNS algorithm (253) and an
overlong algorithm identifier can be stored, then crashes named
when rendered to text. Requires UI:R (user interaction) — someone
must first store the malformed record.
Bugzilla
CVE-2026-10822 dhcp: Key Record using PRIVATEDNS algorithm may lead to exit [fedora-all]
bugzilla·2026-09-01·CVSS 6.5
CVE-2026-10822 [MEDIUM] CVE-2026-10822 dhcp: Key Record using PRIVATEDNS algorithm may lead to exit [fedora-all]
CVE-2026-10822 dhcp: Key Record using PRIVATEDNS algorithm may lead to exit [fedora-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
A KEY/DNSKEY record with PRIVATEDNS algorithm (253) and an
overlong algorithm identifier can be stored, then crashes named
when rendered to text. Requires UI:R (user interaction) — someone
must first store the malformed record.
Bugzilla
CVE-2026-10822 bind: bind9: Key Record using PRIVATEDNS algorithm may lead to exit
bugzilla·2026-07-21·CVSS 6.5
CVE-2026-10822 [MEDIUM] CVE-2026-10822 bind: bind9: Key Record using PRIVATEDNS algorithm may lead to exit
CVE-2026-10822 bind: bind9: Key Record using PRIVATEDNS algorithm may lead to exit
A KEY/DNSKEY record with PRIVATEDNS algorithm (253) and an
overlong algorithm identifier can be stored, then crashes named
when rendered to text. Requires UI:R (user interaction) — someone
must first store the malformed record.
2026-07-22
Published