CVE-2026-10822

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-07-22. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
Trending — 3 sources updated this week
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
KEV
Not listed

Published

July 22, 2026

Last Modified

July 22, 2026

Advisory Details (3)

Auto-updated Jul 22, 2026
No patch confirmed yet.
generic

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

https://kb.isc.org/docs/cve-2026-10822
generic

Index of /isc/bind9/9.21.24

https://downloads.isc.org/isc/bind9/9.21.24
generic

Index of /isc/bind9/9.20.26

https://downloads.isc.org/isc/bind9/9.20.26

Vendor Advisories for CVE-2026-10822(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 9× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 03:04 UTCEG score recompute
  2. 2026-07-22 21:59 UTCEG score recompute
  3. 2026-07-22 21:59 UTCGHSA enrichment
  4. 2026-07-22 19:07 UTCEG score recompute
  5. 2026-07-22 19:07 UTCGHSA enrichment
  6. 2026-07-22 17:10 UTCEG score recompute
  7. 2026-07-22 17:09 UTCGHSA enrichment
  8. 2026-07-22 14:48 UTCEG score recompute
  9. 2026-07-22 14:46 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-10822?
CVE-2026-10822 is a medium vulnerability published on July 22, 2026. 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…
When was CVE-2026-10822 disclosed?
CVE-2026-10822 was first published in the National Vulnerability Database on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-10822?
CVE-2026-10822 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-10822?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10822, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-10822

Explore →

Is Your Infrastructure Affected by CVE-2026-10822?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.