CVE-2026-123595: hickory-dns · Insufficient Verification of Data Authenticity
Affects hickory-dnsSource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 0.26.2 soon.
Data as of 8 Nov 2026, 02:02 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.7 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 8.8 |
- Patch
- Available – fixed in 0.26.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/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 7 Nov 2026.
What to do
Upgrade hickory-dns to 0.26.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| hickory-dnshickory-dns | Affected
| Fixed in– |
| hickory-dnshickory-dns | Affected
| Fixed in
|
crates.iohickory-dnspkg:cargo/hickory-dnsOther 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
Upgrade Hickory DNS to version 0.26.2 or later, where this DNSSEC validation flaw in the NSEC3 handler is fixed. No other mitigation is indicated by the vendor advisory.
Description
CVE-2026-123595 is a high-severity vulnerability in Hickory DNS affecting versions 0.25 through 0.26.0-alpha.1 and 0.26.0-beta.1 before 0.26.2. It involves a DNSSEC validation flaw in the validating recursor's NSEC3 handler, which improperly verifies nonexistence proofs by matching hashes without checking the type bitmap. This flaw allows an attacker to cause NXDOMAIN or NODATA responses with AD=1 to be cached, effectively denying resolution of existing domain names at and below the zone cut. The issue is fixed in version 0.26.2.