CVE-2026-11622

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-22. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

A DNSSEC validating resolver that is under a random subdomain attack against a DNSSEC-signed zone can suffer from runaway memory usage. The attacker needs to be able to send queries faster than the resolver can perform validation. The increased memory usage can be orders of magnitude beyond the limit configured in the max-cache-size parameter. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
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-11622: Potential memory usage beyond configured limits

https://kb.isc.org/docs/cve-2026-11622
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

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntudnsutils (1:9.18.39-0ubuntu0.24.04.6) @ noble2026-09-16ubuntu
redhatbind-32:9.11.4-26.P2.el7_9.212026-08-26redhat
redhatrhcos-4.22.9.8.202608191915-02026-08-25redhat
redhatbind-32:9.16.23-18.el9_4.122026-08-19redhat
redhatbind9.18-32:9.18.29-14.el9_8.82026-08-17redhat
redhatbind-32:9.16.23-31.el9_6.42026-08-17redhat
redhatbind-32:9.18.33-15.el10_2.102026-08-17redhat
redhatbind9.16-32:9.16.23-0.22.el8_10.122026-08-13redhat
redhatbind-32:9.11.36-16.el8_10.142026-08-13redhat
redhatbind-32:9.16.23-40.el9_8.82026-08-13redhat
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

(7 across 7 ecosystems)
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
bind9.20.26-r0
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
bind9.20.26-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
bind9.20.26-r0
Debian:11(1)
PackageVulnerable rangeFixed inDependents
bind91:9.16.15-1 ... 1:9.16.50-1~deb11u5 (17 versions)1:9.16.50-1~deb11u6
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(1)

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 31× in last 7d / 135× 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 261 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-11622?
CVE-2026-11622 is a high vulnerability published on July 22, 2026. A DNSSEC validating resolver that is under a random subdomain attack against a DNSSEC-signed zone can suffer from runaway memory usage. The attacker needs to be able to send queries faster than the resolver can perform validation. The increased memory usage can be orders of magnitude beyond the…
When was CVE-2026-11622 disclosed?
CVE-2026-11622 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-11622 actively exploited?
CVE-2026-11622 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.1% of all scored CVEs.
What is the CVSS score of CVE-2026-11622?
CVE-2026-11622 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-11622?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11622, 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-11622

Explore →

Is Your Infrastructure Affected by CVE-2026-11622?

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