CVSS 4.0
8.7 highCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NCVE-2026-123607 Hickory DNS NSEC3 Closest-Encloser Proof Unbounded Loop Denial of Service
High (8.7) in hickory-dns hickory-dns. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in hickory-net 0.26.1.
On this page
Hickory DNS hickory-proto 0.25.0-alpha.3 through 0.25.2 and hickory-net before 0.26.1 contain an unbounded loop vulnerability in DnssecDnsHandle NSEC3 closest-encloser proof validation when the SOA owner is not an ancestor of the QNAME. Upstream attackers can return NoData or NXDomain responses with a cross-zone SOA record to panic debug builds or exhaust memory in release builds.
Severity
CVSS 3.1
7.5 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H- EPSS
- 0.3% estimated probability of exploitation activity in the next 30 days; 28th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-835 Loop with Unreachable Exit Condition (Infinite Loop)
- Published
- Modified
- Assigned by
- VulnCheck (CNA)
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-123607 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123607?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123607?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-123607 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-123607)
HTML:
<a href="https://cve.bz/cve/CVE-2026-123607"><img src="https://cve.bz/cve/badge/CVE-2026-123607.svg" alt="CVE-2026-123607"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| hickory-dns | from 0.25.0-alpha.3 through 0.25.2 |
| hickory-dns | from 0.26.0-alpha.1 before 0.26.1 |
Fix and patched versions
hickory-net(crates.io): fixed in 0.26.1hickory-proto(crates.io): fixed in 0.26.0-beta.1
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-3v94-mw7p-v465 | crates.io | hickory-proto | >=0.25.0-alpha.3 <=0.25.2 | no fix published |
| GHSA-3v94-mw7p-v465 | crates.io | hickory-net | >=0.26.0-alpha.1 <0.26.1 | 0.26.1 |
| RUSTSEC-2026-0118 | crates.io | hickory-proto | >=0.25.0-alpha.3 <0.26.0-beta.1 | 0.26.0-beta.1 |
| RUSTSEC-2026-0120 | crates.io | hickory-net | >=0.0.0-0 <0.26.1 | 0.26.1 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Ubuntu | 24.04:LTS, 26.04:LTS, 26.10 | rust-hickory-proto | no fix listed | UBUNTU-CVE-2026-123607 |
From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.
History
- The NVD deferred its analysis
Changes since this site first stored the record. The same for every record: /api/public/changes.