The issue is a resource exhaustion vulnerability associated with DNSSEC validation. BIND always validates all RRSIG records in an answer, even if they are not strictly needed. A query to an authoritative server/zone which returns many valid but superfluous RRSIG records causes the validator to waste disproportionate CPU time. This issue affects BIND 9 versions 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, and 9.20.9-S1 through 9.20.24-S1.
CVE-2026-11605
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.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- 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 computedSeverity75% × 45%Exploitation1% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 41%
- KEV
- Not listed
Published
July 22, 2026
Last Modified
July 22, 2026
Advisory Details (3)
Auto-updated Jul 22, 2026CVE-2026-11605: Unnecessary validation of DNSSEC signed records
https://kb.isc.org/docs/cve-2026-11605Vendor Advisories for CVE-2026-11605(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | bind-main-9.18.50-22.hum1 | 2026-07-21 | redhat |
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.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 20× in last 7d / 20× 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.
- 2026-07-26 22:51 UTCEG score recompute
- 2026-07-26 22:51 UTCVendor advisory
- 2026-07-26 22:51 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 09:48 UTCEG score recompute
- 2026-07-26 09:48 UTCVendor advisory
- 2026-07-26 09:48 UTCGHSA enrichment
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:04 UTCEG score recompute
- 2026-07-22 21:59 UTCEG score recompute
- 2026-07-22 21:59 UTCGHSA enrichment
- 2026-07-22 19:05 UTCEG score recompute
- 2026-07-22 19:04 UTCGHSA enrichment
- 2026-07-22 17:10 UTCEG score recompute
- 2026-07-22 17:09 UTCGHSA enrichment
- 2026-07-22 14:48 UTCEG score recompute
- 2026-07-22 14:46 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-11605?
When was CVE-2026-11605 disclosed?
Is CVE-2026-11605 actively exploited?
What is the CVSS score of CVE-2026-11605?
How do I remediate CVE-2026-11605?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-11605
Is Your Infrastructure Affected by CVE-2026-11605?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.