CVE-2026-123607: Hickory proto · NSEC3 closest-encloser proof validation enters unbounded loop on cross-zone responses
Affects hickory-protoSource GCVE Database
Not known to be exploited · CVSS 8.7 High : upgrade to 0.26.0-beta.1 soon.
Data as of 9 Nov 2026, 11:23 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.7 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 7.5 |
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.26.0-beta.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Upgrade hickory-proto to 0.26.0-beta.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
crates.iohickory-protopkg:cargo/hickory-protoOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should update to Hickory proto version 0.26.0-beta.1 or later, where the issue is fixed and the affected code migrated to Hickory net. Applying this update will prevent the unbounded loop and associated denial-of-service. No other mitigations are indicated.
Description
A vulnerability in the Hickory proto library's DNSSEC validation logic causes an unbounded loop when validating certain DNS responses with mismatched SOA records. This can lead to a denial-of-service via memory exhaustion in release builds or a panic in debug builds. The issue affects versions from 0.25.0-alpha.3 up to but not including 0.26.0-beta.1 and is fixed in 0.26.0-beta.1.