CVE-2026-10822: CWE-617 Reachable Assertion in ISC BIND 9
A reachable assertion vulnerability exists in ISC BIND 9 when processing DNS records with a PRIVATEDNS algorithm (253) that specify an invalid length longer than the actual identifier data. This causes BIND to store invalid data and potentially abort when rendering the record to text. The issue affects multiple BIND 9 versions including 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, and 9.21.0 through 9.21.23, including some S1 variants.
AI Analysis
Technical Summary
CVE-2026-10822 is a reachable assertion vulnerability in ISC BIND 9 DNS server software. When BIND encounters a DNS record with a PRIVATEDNS algorithm (253) that improperly specifies a length longer than the actual identifier data, it stores this invalid data. Later, if BIND attempts to render this record to text, it uses the invalid length during processing, causing a consistency check to fail and potentially leading to an abort and exit of the BIND process. This 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, and certain S1 variants. The vulnerability has a CVSS 3.1 base score of 6.5, indicating a medium severity with network attack vector, low attack complexity, no privileges required, user interaction required, unchanged scope, no confidentiality or integrity impact, but high availability impact.
Potential Impact
Successful exploitation causes BIND to abort and exit, resulting in a denial of service condition. There is no impact on confidentiality or integrity, but availability of the DNS service is affected.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a patch or official fix is available, administrators should monitor for updates from ISC and consider mitigating exposure to untrusted DNS data that could trigger this condition. No official fix or temporary workaround is currently documented.
CVE-2026-10822: CWE-617 Reachable Assertion in ISC BIND 9
Description
A reachable assertion vulnerability exists in ISC BIND 9 when processing DNS records with a PRIVATEDNS algorithm (253) that specify an invalid length longer than the actual identifier data. This causes BIND to store invalid data and potentially abort when rendering the record to text. The issue affects multiple BIND 9 versions including 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, and 9.21.0 through 9.21.23, including some S1 variants.
CVSS v3.1
Score 6.5medium
Affected software
pkg:github/isc/bind9Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-10822 is a reachable assertion vulnerability in ISC BIND 9 DNS server software. When BIND encounters a DNS record with a PRIVATEDNS algorithm (253) that improperly specifies a length longer than the actual identifier data, it stores this invalid data. Later, if BIND attempts to render this record to text, it uses the invalid length during processing, causing a consistency check to fail and potentially leading to an abort and exit of the BIND process. This 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, and certain S1 variants. The vulnerability has a CVSS 3.1 base score of 6.5, indicating a medium severity with network attack vector, low attack complexity, no privileges required, user interaction required, unchanged scope, no confidentiality or integrity impact, but high availability impact.
Potential Impact
Successful exploitation causes BIND to abort and exit, resulting in a denial of service condition. There is no impact on confidentiality or integrity, but availability of the DNS service is affected.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a patch or official fix is available, administrators should monitor for updates from ISC and consider mitigating exposure to untrusted DNS data that could trigger this condition. No official fix or temporary workaround is currently documented.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- isc
- Date Reserved
- 2026-06-04T07:51:13.246Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a60d93c9c2644c7f83639ef
Added to database: 07/22/2026, 14:52:44 UTC
Last enriched: 07/22/2026, 15:08:35 UTC
Last updated: 07/22/2026, 16:24:45 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.