Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By isc

  2. · 48 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-10822, by who scored it
Scored byCVSSScoreVector
iscCNA (assigner)3.1Medium6.5CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVDNVD · Analyzed3.1Medium6.5CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.42% · top 63% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.5.

Affected products

  • ISC · BIND 9

    • affected 9.18.0 – ≤ 9.18.50
    • affected 9.20.0 – ≤ 9.20.24
    • affected 9.21.0 – ≤ 9.21.23
    • affected 9.18.11-S1 – ≤ 9.18.50-S1
    • affected 9.20.9-S1 – ≤ 9.20.24-S1

What to do

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.

Workaround: No workarounds known.

Exploitation: This flaw was discovered in internal testing. We are not aware of any active exploits.

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-10822 badge
[![CVE-2026-10822](https://cveledger.app/badge/CVE-2026-10822.svg)](https://cveledger.app/cve/CVE-2026-10822)

Record last updated .