CVE-2026-10822
Reported by isc · Published July 22, 2026
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.
Risk Scores
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| ISC | BIND 9 | 9.18.0, 9.20.0, 9.21.0 |
| alpine | bind | 0, 0, 0 |
| isc | bind | 9.18.0, 9.20.0, 9.21.0 |
| ISC | BIND 9 | 9.18.0, 9.20.0, 9.21.0 |
Timeline
- Jul 22, 2026 Coalition ESS Score
- Jul 22, 2026 CVE Published
- Jul 22, 2026 CVE Updated
- Jul 23, 2026 Security Advisory
- Jul 25, 2026 EPSS Score
References
- CVE-2026-10822 vendor-advisory
- patch
- patch