← Back to CVE Explorer

CVE-2026-10822

Full vulnerability record from the local CVENow database.

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.

Severity
MEDIUM
CVSS score
6.5 (v3.1)
Vulnerability status
Undergoing Analysis
Source identifier
Published
2026-07-22 15:16:51.330000
Last modified
2026-10-24 18:10:00.163000
View original CVE JSON
{
  "id": "CVE-2026-10822",
  "sourceIdentifier": "[email protected]",
  "published": "2026-07-22T15:16:51.330",
  "lastModified": "2026-10-24T18:10:00.163",
  "vulnStatus": "Undergoing Analysis",
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "If BIND encounters a particular invalid data structure in a DNS record, it will accept the invalid data, and may subsequently abort and exit.\n\nBIND 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.\nThis 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."
    },
    {
      "lang": "es",
      "value": "Si BIND encuentra una estructura de datos inválida particular en un registro DNS, aceptará los datos inválidos y posteriormente puede abortar y salir.\n\nBIND primero necesitará almacenar un registro DNS para una clave (KEY, DNSKEY, etc.). Esa clave debe especificar un algoritmo PRIVATEDNS (253), y en el identificador del algoritmo, dar incorrectamente una longitud mayor que los datos reales del identificador. El identificador inválido será almacenado. Si BIND posteriormente necesita renderizar ese registro a texto, usará la longitud inválida durante el procesamiento, lo que llevará a que falle una verificación de consistencia.\nEste problema afecta a las versiones de BIND 9 9.18.0 a 9.18.50, 9.20.0 a 9.20.24, 9.21.0 a 9.21.23, 9.18.11-S1 a 9.18.50-S1, y 9.20.9-S1 a 9.20.24-S1."
    }
  ],
  "affected": [
    {
      "source": "[email protected]",
      "affectedData": [
        {
          "vendor": "ISC",
          "product": "BIND 9",
          "defaultStatus": "unaffected",
          "versions": [
            {
              "version": "9.18.0",
              "lessThanOrEqual": "9.18.50",
              "versionType": "custom",
              "status": "affected"
            },
            {
              "version": "9.20.0",
              "lessThanOrEqual": "9.20.24",
              "versionType": "custom",
              "status": "affected"
            },
            {
              "version": "9.21.0",
              "lessThanOrEqual": "9.21.23",
              "versionType": "custom",
              "status": "affected"
            },
            {
              "version": "9.18.11-S1",
              "lessThanOrEqual": "9.18.50-S1",
              "versionType": "custom",
              "status": "affected"
            },
            {
              "version": "9.20.9-S1",
              "lessThanOrEqual": "9.20.24-S1",
              "versionType": "custom",
              "status": "affected"
            }
          ]
        }
      ]
    }
  ],
  "metrics": {
    "cvssMetricV31": [
      {
        "source": "[email protected]",
        "type": "Secondary",
        "cvssData": {
          "version": "3.1",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
          "baseScore": 6.5,
          "baseSeverity": "MEDIUM",
          "attackVector": "NETWORK",
          "attackComplexity": "LOW",
          "privilegesRequired": "NONE",
          "userInteraction": "REQUIRED",
          "scope": "UNCHANGED",
          "confidentialityImpact": "NONE",
          "integrityImpact": "NONE",
          "availabilityImpact": "HIGH"
        },
        "exploitabilityScore": 2.8,
        "impactScore": 3.6
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "timestamp": "2026-07-22T18:53:26.146110Z",
          "id": "CVE-2026-10822",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "version": "2.0.3"
        }
      }
    ]
  },
  "weaknesses": [
    {
      "source": "[email protected]",
      "type": "Secondary",
      "description": [
        {
          "lang": "en",
          "value": "CWE-617"
        },
        {
          "lang": "en",
          "value": "CWE-1284"
        }
      ]
    }
  ],
  "references": [
    {
      "url": "https://downloads.isc.org/isc/bind9/9.20.26",
      "source": "[email protected]"
    },
    {
      "url": "https://downloads.isc.org/isc/bind9/9.21.24",
      "source": "[email protected]"
    },
    {
      "url": "https://kb.isc.org/docs/cve-2026-10822",
      "source": "[email protected]"
    }
  ]
}