MediumCVE-2026-10822

    Key Record using PRIVATEDNS algorithm may lead to unexpected exit (CVE-2026-10822)

    Published Last modified Sources: Ubuntu, Debian, BSI, Red Hat, CVE.org, Msrc Update Guide

    What is affected, what to do

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

    Update BIND to version 9.20.26, BIND Supported Preview Edition to version 9.20.26-S1, LANTIME to version V7.10.014.

    Affected
    • ISC BIND 9 lte 9.18.0..9.18.50
    • ISC BIND 9 lte 9.20.0..9.20.24
    • ISC BIND 9 lte 9.21.0..9.21.23
    • ISC BIND 9 lte 9.18.11-S1..9.18.50-S1
    • ISC BIND 9 lte 9.20.9-S1..9.20.24-S1

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    6.5

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    6.5

    CVSS v3

    Severity Medium on the scale from 0 to 10.

    Source: Ubuntu, Debian, BSI, Red Hat, CVE.org, Msrc Update Guide

    0.4 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 32.0

    Show all metrics
    Severity
    Medium
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    62.01 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    6.5 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    6.5
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.4 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    32.0
    Elevated — this CVE ranks above at least 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 22 July 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-617, CWE-1284

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    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.

    Source: Ubuntu Security Notices, Debian Security Advisories, BSI WID Portal, BSI CSAF, redhat_csaf, cvelistv5, NVD (NIST), Microsoft Security Update Guide

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    ISCBIND 9
    • 9.18.11-S1 – ≤ 9.18.50-S1
    • 9.20.9-S1 – ≤ 9.20.24-S1
    • 9.21.0 – ≤ 9.21.23
    • 9.20.0 – ≤ 9.20.24
    • 9.18.0 – ≤ 9.18.50
    • —
    • —
    • —
    • —
    • —
    Internet Systems ConsortiumBIND
    • < 9.20.26
    • < 9.21.24
    • 9.20.26
    • 9.21.24
    Internet Systems ConsortiumBIND Supported Preview Edition
    • < 9.20.26-S1
    • 9.20.26-S1
    MeinbergLANTIME
    • < V7.10.014
    • V7.10.014

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxdebianbind9trixie
    Linuxubuntubind9bionic
    Linuxubuntubind9focal
    Linuxubuntubind9jammy
    Linuxubuntubind9noble
    Linuxubuntubind9resolute
    Linuxubuntubind9trusty
    Linuxubuntubind9xenial

    Weakness classes (CWE)

    • CWE-617Reachable Assertion

      Base

      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.

      Entry at MITRE CWE-617

    • CWE-1284Improper Validation of Specified Quantity in Input

      Base

      The product receives input that is expected to specify a quantity (such as size or length), but it does not validate or incorrectly validates that the quantity has the required properties.

      Entry at MITRE CWE-1284

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: none known, automatable: no

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentadded
      —
      {"id":"CVE-2026-10822","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-07-22T18:53:26.146110Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. Receivedisc.org

      CVSS V3.1: AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

      Weakness type: CWE-617, CWE-1284

      Description added or changed

      Show 8 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Affected versions (publisher)added
      —
      BIND 9
      Descriptionadded
      —
      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.
      CVSSadded
      —
      AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
      Weakness type (CWE)added
      —
      CWE-617
      Weakness type (CWE)added
      —
      CWE-1284
      Referenceadded
      —
      https://downloads.isc.org/isc/bind9/9.20.26
      Referenceadded
      —
      https://downloads.isc.org/isc/bind9/9.21.24
      Referenceadded
      —
      https://kb.isc.org/docs/cve-2026-10822

      Source identifier: security-officer@isc.org

    One NVD translation into another language is hidden.

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-10822
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-10822"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-10822.svg?lang=en" alt="CVE-2026-10822 – NEOSEC Intel" height="20"></a>