CVE-2026-10822

Key Record using PRIVATEDNS algorithm may lead to unexpected exit

Published Jul 22, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

BIND accepts a malformed key record that declares the PRIVATEDNS algorithm and supplies a length field larger than the actual data. The server stores the corrupted identifier and later, when it must render the record to text, uses the invalid length. This triggers a consistency check failure, causing BIND to terminate with an abort, effectively taken offline. The flaw stems from improper validation of data lengths (CWE‑1284) and the improper restriction of internal functions (CWE‑617). It does not permit code execution or privilege escalation, but it results in a denial of service by crashing the DNS server.

Affected Systems

ISC BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, and the corresponding release-S1 builds 9.18.11-S1 through 9.18.50-S1 and 9.20.9-S1 through 9.20.24-S1 are affected.

Risk and Exploitability

The CVSS score of 6.5 places the vulnerability in the medium severity range. The EPSS score is below 1 % indicating a very low probability of exploitation in the wild, and the issue is not listed in the CISA KEV catalog. The likely attack vector is an attacker sending a crafted DNS response that includes the malformed PRIVATEDNS key record, which BIND will accept, store, and later attempt to render, causing a fatal abort. Success requires that the server be reachable from the attacker and that the record be stored in zone data or transferred into the server. The vulnerability does not provide a path to execute arbitrary code or elevate privileges.

Remediation

Vendor Solution

Upgrade to the patched release most closely related to your current version of BIND 9: 9.20.26, 9.21.24, or 9.20.26-S1.


Vendor Workaround

No workarounds known.


OpenCVE Recommended Actions

  • Upgrade ISC BIND 9 to the patched releases 9.20.26, 9.21.24, or 9.20.26-S1.
  • After upgrading, review zone files and SRS data to remove or correct any KEY, DNSKEY, or related records that use the PRIVATEDNS algorithm, ensuring malformed records cannot be re‑introduced.
  • Configure logging or alerting to detect fatal exits or abort messages so that any future crash due to a malformed record can be promptly identified.

Generated by OpenCVE AI on August 3, 2026 at 23:36 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4725-1 bind9 security update
Debian DSA Debian DSA DSA-6395-1 bind9 security update
Ubuntu USN Ubuntu USN USN-8648-1 Bind vulnerabilities
Ubuntu USN Ubuntu USN USN-8929-1 Bind vulnerabilities
History
Type Values Removed Values Added
CPEs cpe:2.3:a:isc:bind:*:*:*:*:-:*:*:*
cpe:2.3:a:isc:bind:*:*:*:*:supported_preview:*:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Key Record using PRIVATEDNS algorithm may lead to unexpected exit
First Time appeared Isc
Isc bind
Weaknesses CWE-1284
CWE-617
CPEs cpe:2.3:a:isc:bind:*:*:*:*:*:*:*:*
Vendors & Products Isc
Isc bind
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H'}

Weaknesses
  • CWE-1284

    Improper Validation of Specified Quantity in Input

  • CWE-617

    Reachable Assertion

Sources

Status
PUBLISHED
Assigner
isc
Published
Updated
Jul 22, 2026, 6:53 PM
Reserved
Jun 4, 2026, 7:51 AM
Status
Analyzed
Published
Jul 22, 2026, 3:16 PM
Modified
Nov 2, 2026, 5:46 PM
Severity
Moderate
Public date
Jul 22, 2026, 12:00 AM