Skip to main content
Mallory
MediumVulnerability

CVE-2026-10822: BIND 9 PRIVATEDNS Key Record Denial of Service

Published Jul 22, 2026 · Updated 12 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days5 mentions · peak 2 in a dayToday
CVSS6.5Medium · v3.1
EPSS0.42%37th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Internet Systems Consortium
IdentifiersCVE-2026-10822CWE-617 · Reachable Assertion

BIND 9 accepts and stores malformed DNS key records, including KEY and DNSKEY records, using the PRIVATEDNS algorithm (253) with an algorithm-identifier length exceeding the available identifier data. When the stored record is subsequently rendered to text, BIND processes the invalid length, causing an internal consistency check to fail and the named process to abort. Affected versions are 9.18.0–9.18.50, 9.20.0–9.20.24, 9.21.0–9.21.23, 9.18.11-S1–9.18.50-S1, and 9.20.9-S1–9.20.24-S1. Vendor packages may contain backported fixes without changing the upstream version.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation terminates the BIND named process, disrupting DNS service availability. F5 BIG-IP DNS systems using the affected BIND functionality can also experience denial of service. No confidentiality or integrity impact is established for this vulnerability.

Mitigation

If you can’t patch tonight, do this now.

For F5 BIG-IP DNS, disable "Use BIND Server on BIG-IP" in the applicable DNS profile, or restrict DNS recursion. Disabling BIND can affect configurations that depend on it for fallback resolution. Restricting recursive DNS access to trusted clients can reduce exposure but does not replace patching.

Remediation

Patch, then assume compromise.

Install vendor-provided BIND security updates. Debian stable (trixie) provides the fix in bind9 version 1:9.20.26-1~deb13u1 or later. Ubuntu USN-8648-1 provides corrected packages for Ubuntu 26.04 LTS in 1:9.20.24-1ubuntu0.2, Ubuntu 24.04 LTS in 1:9.18.39-0ubuntu0.24.04.6, and Ubuntu 22.04 LTS in 1:9.18.39-0ubuntu0.22.04.5; subsequent security updates also incorporate these fixes. For F5 BIG-IP DNS, install a release or hotfix explicitly identified by F5 as fixed; no fixed BIG-IP version is identified in the available advisory.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Internet Systems ConsortiumBindapplication
FAQ

Frequently asked questions

Is CVE-2026-10822 exploited in the wild?
As of Nov 6, 2026, Mallory has no reports of CVE-2026-10822 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-10822?
As of Nov 6, 2026, Mallory has found no public exploit for CVE-2026-10822.
Is there a patch for CVE-2026-10822?
Install vendor-provided BIND security updates. Debian stable (trixie) provides the fix in bind9 version 1:9.20.26-1~deb13u1 or later.
What products are affected by CVE-2026-10822?
Internet Systems Consortium Bind.
How severe is CVE-2026-10822?
CVE-2026-10822 has a CVSS v3.1 score of 6.5 (Medium) and an EPSS score of 0.42% (37th percentile) as of Nov 6, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.