# 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.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **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:** Yes
- **Published:** 22 Jul 2026
- **Updated:** 22 Jul 2026
- **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, MINI-886g-4p46-5c2q, MINI-8h64-fr2m-7wcp, MINI-h926-v2jv-2868, UBUNTU-CVE-2026-10822

## 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.

Weakness: CWE-617 (Reachable Assertion), CWE-1284 (Improper Validation of Specified Quantity in Input)

## Which versions are affected by CVE-2026-10822?


## How do I fix CVE-2026-10822?

Apply the vendor's patch.

## Is CVE-2026-10822 being exploited?

There is no known exploitation of CVE-2026-10822 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10822 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-10822 in the wild and no public exploit code.

Affected product: ISC BIND 9. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10822/ (Markdown: https://insights.sbomify.com/CVE-2026-10822/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10822
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10822
- OSV: https://osv.dev/vulnerability/CVE-2026-10822

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10822/
Summaries are generated and may contain mistakes; the official description above is the record.