CVE-2026-10822

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM 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: epss, ghsa, secondary
Trending — 4 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

A fix is available — apply it.

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(medium)
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 PROB
0%
EPSS %ILE
32%
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(3)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntubind9-utils (1:9.20.24-1ubuntu0.2) @ resolute2026-09-14ubuntu
redhatbind-main-9.20.26-0.1.hum12026-08-12redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 6 ecosystems)
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
bind—9.20.26-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
bind—9.20.26-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
bind—9.20.26-r0—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
bind91:9.18.12-1 ... 1:9.18.49-1~deb12u1 (16 versions)1:9.18.49-1~deb12u2—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
bind91:9.20.11-4 ... 1:9.20.26-1~deb13u1~bpo12+1 (21 versions)1:9.20.26-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
bind91:9.20.11-4 ... 1:9.20.26-1~deb13u1~bpo12+1 (22 versions)1:9.20.26-1—

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 22× in last 7d / 96× 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.

Showing the most recent 100 of 177 total refreshes for this CVE.

  1. 2026-09-14 16:49 UTCEG score recompute
  2. 2026-09-14 16:49 UTCVendor advisory
  3. 2026-09-14 16:49 UTCGHSA enrichment
  4. 2026-09-13 16:46 UTCEPSS rescore
  5. 2026-09-13 15:28 UTCVendor advisory
  6. 2026-09-13 15:28 UTCGHSA enrichment
  7. 2026-09-12 17:12 UTCEG score recompute
  8. 2026-09-12 17:12 UTCVendor advisory
  9. 2026-09-12 17:12 UTCGHSA enrichment
  10. 2026-09-12 15:00 UTCEPSS rescore
  11. 2026-09-11 19:33 UTCEG score recompute
  12. 2026-09-11 19:33 UTCVendor advisory
  13. 2026-09-11 19:33 UTCGHSA enrichment
  14. 2026-09-11 14:52 UTCEPSS rescore
  15. 2026-09-11 09:36 UTCEPSS rescore
  16. 2026-09-10 21:33 UTCEG score recompute
  17. 2026-09-10 21:33 UTCVendor advisory
  18. 2026-09-10 21:33 UTCGHSA enrichment
  19. 2026-09-10 09:34 UTCEPSS rescore
  20. 2026-09-09 09:16 UTCEG score recompute
  21. 2026-09-09 09:16 UTCVendor advisory
  22. 2026-09-09 09:16 UTCGHSA enrichment
  23. 2026-09-08 22:00 UTCEPSS rescore
  24. 2026-09-07 21:41 UTCEG score recompute
  25. 2026-09-07 21:41 UTCVendor advisory
Show 75 more
  1. 2026-09-07 21:41 UTCGHSA enrichment
  2. 2026-09-07 16:01 UTCEPSS rescore
  3. 2026-09-06 17:29 UTCEG score recompute
  4. 2026-09-06 17:29 UTCVendor advisory
  5. 2026-09-06 17:29 UTCGHSA enrichment
  6. 2026-09-06 13:47 UTCEPSS rescore
  7. 2026-09-05 19:34 UTCEG score recompute
  8. 2026-09-05 19:34 UTCVendor advisory
  9. 2026-09-05 19:34 UTCGHSA enrichment
  10. 2026-09-04 13:54 UTCEG score recompute
  11. 2026-09-04 13:54 UTCVendor advisory
  12. 2026-09-04 13:54 UTCGHSA enrichment
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:11 UTCEPSS rescore
  15. 2026-09-01 23:40 UTCEG score recompute
  16. 2026-09-01 23:40 UTCVendor advisory
  17. 2026-09-01 23:40 UTCGHSA enrichment
  18. 2026-09-01 13:53 UTCEPSS rescore
  19. 2026-08-30 22:31 UTCEG score recompute
  20. 2026-08-30 22:31 UTCVendor advisory
  21. 2026-08-30 22:31 UTCGHSA enrichment
  22. 2026-08-30 19:17 UTCEPSS rescore
  23. 2026-08-30 01:21 UTCEPSS rescore
  24. 2026-08-30 00:53 UTCEG score recompute
  25. 2026-08-30 00:53 UTCVendor advisory
  26. 2026-08-30 00:53 UTCGHSA enrichment
  27. 2026-08-28 21:40 UTCEPSS rescore
  28. 2026-08-27 23:46 UTCEG score recompute
  29. 2026-08-27 23:46 UTCVendor advisory
  30. 2026-08-27 23:46 UTCGHSA enrichment
  31. 2026-08-27 14:24 UTCEPSS rescore
  32. 2026-08-27 02:06 UTCEG score recompute
  33. 2026-08-27 02:06 UTCVendor advisory
  34. 2026-08-27 02:06 UTCGHSA enrichment
  35. 2026-08-26 04:28 UTCEG score recompute
  36. 2026-08-26 04:28 UTCVendor advisory
  37. 2026-08-26 04:28 UTCGHSA enrichment
  38. 2026-08-25 13:48 UTCEPSS rescore
  39. 2026-08-25 06:42 UTCEG score recompute
  40. 2026-08-25 06:42 UTCVendor advisory
  41. 2026-08-25 06:42 UTCGHSA enrichment
  42. 2026-08-24 08:55 UTCVendor advisory
  43. 2026-08-24 08:55 UTCGHSA enrichment
  44. 2026-08-23 11:14 UTCEG score recompute
  45. 2026-08-23 11:14 UTCVendor advisory
  46. 2026-08-23 11:14 UTCGHSA enrichment
  47. 2026-08-23 00:19 UTCEPSS rescore
  48. 2026-08-22 13:37 UTCEG score recompute
  49. 2026-08-22 13:37 UTCVendor advisory
  50. 2026-08-22 13:37 UTCGHSA enrichment
  51. 2026-08-21 23:48 UTCEPSS rescore
  52. 2026-08-21 15:59 UTCEG score recompute
  53. 2026-08-21 15:59 UTCVendor advisory
  54. 2026-08-21 15:59 UTCGHSA enrichment
  55. 2026-08-20 22:55 UTCEPSS rescore
  56. 2026-08-20 18:21 UTCVendor advisory
  57. 2026-08-20 18:21 UTCGHSA enrichment
  58. 2026-08-19 20:44 UTCEG score recompute
  59. 2026-08-19 20:44 UTCVendor advisory
  60. 2026-08-19 20:44 UTCGHSA enrichment
  61. 2026-08-19 17:03 UTCEPSS rescore
  62. 2026-08-18 23:05 UTCEG score recompute
  63. 2026-08-18 23:05 UTCVendor advisory
  64. 2026-08-18 23:05 UTCGHSA enrichment
  65. 2026-08-18 13:48 UTCEPSS rescore
  66. 2026-08-18 01:28 UTCEG score recompute
  67. 2026-08-18 01:28 UTCVendor advisory
  68. 2026-08-18 01:28 UTCGHSA enrichment
  69. 2026-08-17 03:40 UTCEG score recompute
  70. 2026-08-17 03:40 UTCVendor advisory
  71. 2026-08-17 03:40 UTCGHSA enrichment
  72. 2026-08-16 14:56 UTCEPSS rescore
  73. 2026-08-16 06:02 UTCEG score recompute
  74. 2026-08-16 06:02 UTCVendor advisory
  75. 2026-08-16 06:02 UTCGHSA enrichment

Frequently asked(5)

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.
Is CVE-2026-10822 actively exploited?
CVE-2026-10822 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 68.4% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs