Skip to main content
VulnerabilityPublished

CVE-2026-123607: hickory-dns · Infinite Loop

Affects hickory-dnsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 0.26.1 soon.

Data as of 8 Nov 2026, 01:50 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.7
CNA (VulnCheck)CVSS 3.17.5
Patch
Available – fixed in 0.26.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 7 Nov 2026.

What to do

Upgrade hickory-dns to 0.26.1.

Affected software

ProductAffectedFixed in
hickory-dnshickory-dnsAffected
  • >=0.25.0-alpha.3 <=0.25.2
Fixed in–
hickory-dnshickory-dnsAffected
  • >=0.26.0-alpha.1 <0.26.1
Fixed in
  • 0.26.1
crates.iohickory-dnspkg:cargo/hickory-dnsOther threatsAffected
  • >=0.25.0-alpha.3 <=0.25.2
  • >=0.26.0-alpha.1 <0.26.1
Fixed in
  • 0.26.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Hickory DNS to version 0.26.1 or later, where this vulnerability is fixed. No other mitigations are indicated or required. Users should apply this official fix to prevent potential denial of service conditions.

Description

CVE-2026-123607 is a high-severity vulnerability in Hickory DNS affecting versions 0.25.0-alpha.3 through 0.25.2 and 0.26.0-alpha.1 through before 0.26.1. It involves an unbounded loop in the DnssecDnsHandle component during NSEC3 closest-encloser proof validation when the SOA owner is not an ancestor of the QNAME. This can lead to memory exhaustion or panic in debug builds when malicious upstream attackers return crafted NoData or NXDomain responses with cross-zone SOA records. The issue is fixed in version 0.26.1.

References

Community reviews

Loading reviews…