CVE-2026-10822 Key Record using PRIVATEDNS algorithm may lead to unexpected exit
An attacker can cause a denial of service in BIND by submitting a malformed DNS key record with an invalid PRIVATEDNS algorithm length.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-10822?
CVE-2026-10822 is a medium-severity denial of service vulnerability in ISC BIND 9, published on 22 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official 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.
Which versions are affected by CVE-2026-10822?
How do I fix CVE-2026-10822?
Apply the vendor's patch.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2026-10822 being exploited?
There is no known exploitation of CVE-2026-10822 in the wild and no public exploit code.
Sources
Also known as ALPINE-CVE-2026-10822, AZL-93114, BELL-CVE-2026-10822, DEBIAN-CVE-2026-10822, ECHO-6303-1fdb-ed48, GHSA-42qr-f5rc-vfw9 and 4 more.