BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-10822High confidence

Key Record using PRIVATEDNS algorithm may lead to unexpected exit

ISC · BIND 9

6.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.38% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs ISC BIND 9 and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

8 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · mainbindVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.9.20.26-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · mainbindVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.9.20.26-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcebind9Vendor fix publishedDebian records a fixed source-package version for this release.1:9.20.26-1~deb13u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcebind9Vendor fix publishedDebian records a fixed source-package version for this release.1:9.18.49-1~deb12u2Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcebind9Vendor fix publishedDebian records a fixed source-package version for this release.1:9.20.26-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcebind9Vendor fix publishedDebian records a fixed source-package version for this release.1:9.20.26-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivebind9Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.1:9.18.39-0ubuntu0.24.04.6Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archiveisc-dhcpUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-10822 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitybind: bind9: Key Record using PRIVATEDNS algorithm may lead to exit
87 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • bind as a component of Red Hat Enterprise Linux 10
  • bind-chroot as a component of Red Hat Enterprise Linux 10
  • bind-devel as a component of Red Hat Enterprise Linux 10
  • bind-dnssec-utils as a component of Red Hat Enterprise Linux 10
  • bind-doc as a component of Red Hat Enterprise Linux 10
  • bind-libs as a component of Red Hat Enterprise Linux 10
  • bind-license as a component of Red Hat Enterprise Linux 10
  • bind-utils as a component of Red Hat Enterprise Linux 10
  • bind.src as a component of Red Hat Enterprise Linux 10
  • bind as a component of Red Hat Enterprise Linux 6
  • bind-chroot as a component of Red Hat Enterprise Linux 6
  • bind-devel as a component of Red Hat Enterprise Linux 6
Summary
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.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-47705

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

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.

What

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.

Why

The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Reachable Assertion → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-617 ↗

CWE-617: Reachable Assertion. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-617
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-3038Meinberg LANTIME: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Meinberg LANTIME ausnutzen, um beliebigen Code auszuführen, Berechtigungen zu erweitern, Sicherheitsmaßnahmen zu umgehen, sensible Informationen offenzulegen, Daten zu manipulieren oder Denial-of-Service-Zustände herbeizuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-2484Internet Systems Consortium BIND: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Internet Systems Consortium BIND ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand auszulösen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260729Security Bulletin 29 Jul 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 29 Jul 2026, published on 29 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1206Multiples vulnérabilités dans les produits IBM

/CVERecord?id=CVE-2025-9095 Référence CVE CVE-2025-9096 https://www.cve.org/CVERecord?id=CVE-2025-9096 Référence CVE CVE-2026-0846 https://www.cve.org/CVERecord?id=CVE-2026-0846 Référence CVE CVE-2026-0847 https://www.cve.org/CVERecord?id=CVE-2026-0847 Référence CVE CVE-2026-0848 https://www.cve.org/CVERecord?id=CVE-2026-0848 Référence CVE CVE-2026-10050 https://www.cve.org/CVERecord?id=CVE-2026-10050 Référence CVE CVE-2026-10051 https://www.cve.org/CVERecord?id=CVE-2026-10051 Référence CVE CVE-2026-10541 https://www.cve.org/CVERecord?id=CVE-2026-10541 Référence CVE CVE-2026-10723 https://www.cve.org/CVERecord?id=CVE-2026-10723 Référence CVE CVE-2026-10822 https://www.cve.org/CVERecord?id=CVE-2026-10822 Référence CVE CVE-2026-10841 https://www.cve.org/CVERecord?id=CVE-2026-10841 Référence CVE CVE-2026-10842 https://www.cve.org/CVERecord?id=CVE-2026-10842 Référence CVE CVE-2026-11331 https://www.cve.org/CVERecord?id=CVE-2026-11331 Référence CVE CVE-2026-11541 https://www.cve.org/CVERecord?id=CVE-2026-11541 Référence CVE CVE-2026-11548 https://www.cve.org/CVERecord?id=CVE-2026-11548 Référence CVE CVE-2026-11549 https://www.cve.org/CVERecord?id=CVE-2026-11549 Référence CVE CVE-2026-11622 https://www.cve.org/CVERecord?id=CVE-2026-11622 Référence CVE CVE-2026-11721 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-024975ISC BINDにおける複数の脆弱性（2026年7月）

ISC（Internet Systems Consortium）から、ISC BINDの複数の脆弱性が公開されました。 CVE-2026-10723: Incorrect acceptance of NSEC3 records CVE-2026-10822: Key Record using PRIVATEDNS algorithm may lead to unexpected exit CVE-2026-11331: Potential wildcard CNAME RPZ policy bypass CVE-2026-11605: Unnecessary validation of DNSSEC signed records CVE-2026-11622: Potential memory usage beyond configured limits CVE-2026-11721: Cache poisoning possible with label count discrepancy, RRSIG, and wildcards CVE-2026-12617: Record ordering based unexpected exit with CNAME or DNAME CVE-2026-13204: Unexpected exit in certain situations with NSEC and NSEC3 both present CVE-2026-13321: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
Action
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 22 Jul 2026 · Last source change 22 Jul 2026, 18:53 UTC · CWE-617 · Reachable Assertion

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-47705
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enrichment underway

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    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; 9.20.9-S1 ≤ 9.20.24-S1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    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; 9.20.9-S1 ≤ 9.20.24-S1 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    bind as a component of Red Hat Enterprise Linux 10; bind-chroot as a component of Red Hat Enterprise Linux 10; bind-devel as a component of Red Hat Enterprise Linux 10; bind-dnssec-utils as a component of Red Hat Enterprise Linux 10; bind-doc as a component of Red Hat Enterprise Linux 10; bind-libs as a component of Red Hat Enterprise Linux 10; bind-license as a component of Red Hat Enterprise Linux 10; bind-utils as a component of Red Hat Enterprise Linux 10; bind.src as a component of Red Hat Enterprise Linux 10; bind as a component of Red Hat Enterprise Linux 6; bind-chroot as a component of Red Hat Enterprise Linux 6; bind-devel as a component of Red Hat Enterprise Linux 6; bind-libs as a component of Red Hat Enterprise Linux 6; bind-sdb as a component of Red Hat Enterprise Linux 6; bind-utils as a component of Red Hat Enterprise Linux 6; bind.src as a component of Red Hat Enterprise Linux 6; bind as a component of Red Hat Enterprise Linux 7; bind-chroot as a component of Red Hat Enterprise Linux 7; bind-devel as a component of Red Hat Enterprise Linux 7; bind-export-devel as a component of Red Hat Enterprise Linux 7; bind-export-libs as a component of Red Hat Enterprise Linux 7; bind-libs as a component of Red Hat Enterprise Linux 7; bind-libs-lite as a component of Red Hat Enterprise Linux 7; bind-license as a component of Red Hat Enterprise Linux 7; bind-lite-devel as a component of Red Hat Enterprise Linux 7; bind-pkcs11 as a component of Red Hat Enterprise Linux 7; bind-pkcs11-devel as a component of Red Hat Enterprise Linux 7; bind-pkcs11-libs as a component of Red Hat Enterprise Linux 7; bind-pkcs11-utils as a component of Red Hat Enterprise Linux 7; bind-sdb as a component of Red Hat Enterprise Linux 7; and 56 more · Fixed: bind-main@aarch64 as a component of Red Hat Hardened Images; bind-main@noarch as a component of Red Hat Hardened Images; bind-main@src as a component of Red Hat Hardened Images; bind-main@x86_64 as a component of Red Hat Hardened Images
    After
    bind as a component of Red Hat Enterprise Linux 10; bind-chroot as a component of Red Hat Enterprise Linux 10; bind-devel as a component of Red Hat Enterprise Linux 10; bind-dnssec-utils as a component of Red Hat Enterprise Linux 10; bind-doc as a component of Red Hat Enterprise Linux 10; bind-libs as a component of Red Hat Enterprise Linux 10; bind-license as a component of Red Hat Enterprise Linux 10; bind-utils as a component of Red Hat Enterprise Linux 10; bind.src as a component of Red Hat Enterprise Linux 10; bind as a component of Red Hat Enterprise Linux 6; bind-chroot as a component of Red Hat Enterprise Linux 6; bind-devel as a component of Red Hat Enterprise Linux 6; bind-libs as a component of Red Hat Enterprise Linux 6; bind-sdb as a component of Red Hat Enterprise Linux 6; bind-utils as a component of Red Hat Enterprise Linux 6; bind.src as a component of Red Hat Enterprise Linux 6; bind as a component of Red Hat Enterprise Linux 7; bind-chroot as a component of Red Hat Enterprise Linux 7; bind-devel as a component of Red Hat Enterprise Linux 7; bind-export-devel as a component of Red Hat Enterprise Linux 7; bind-export-libs as a component of Red Hat Enterprise Linux 7; bind-libs as a component of Red Hat Enterprise Linux 7; bind-libs-lite as a component of Red Hat Enterprise Linux 7; bind-license as a component of Red Hat Enterprise Linux 7; bind-lite-devel as a component of Red Hat Enterprise Linux 7; bind-pkcs11 as a component of Red Hat Enterprise Linux 7; bind-pkcs11-devel as a component of Red Hat Enterprise Linux 7; bind-pkcs11-libs as a component of Red Hat Enterprise Linux 7; bind-pkcs11-utils as a component of Red Hat Enterprise Linux 7; bind-sdb as a component of Red Hat Enterprise Linux 7; and 57 more · Fixed: bind-main@aarch64 as a component of Red Hat Hardened Images; bind-main@noarch as a component of Red Hat Hardened Images; bind-main@src as a component of Red Hat Hardened Images; bind-main@x86_64 as a component of Red Hat Hardened Images
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-47705↗Red Hat Product Security security advisory↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-10822 · cve.blacktree.nl