CVE-2026-123605: hickory-dns · Improper Verification of Cryptographic Signature
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, 01:50 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
Users of Hickory DNS should upgrade to version 0.26.2 or later, where this vulnerability is fixed. Applying this official fix eliminates the DNSSEC validation bypass. No additional mitigations are indicated or required beyond upgrading to the fixed version.
Description
CVE-2026-123605 is a high-severity vulnerability in Hickory DNS affecting versions 0.1 through 0.25.0-alpha.3 and 0.26.0-beta.1 up to but not including 0.26.2. The flaw allows DNSSEC validation bypass due to improper verification of cryptographic signatures. Specifically, the validator accepts RRSIG signatures against the DNSKEY of any name in the Signer's Name field without confirming that this name matches the zone of the RRset. This enables attackers controlling any secure zone to forge valid signatures over arbitrary records in unrelated zones, potentially misleading resolvers, recursors, and clients using DnssecDnsHandle into accepting unauthenticated data as authentic. The issue is fixed in version 0.26.2.