CVE-2026-123599: hickory-dns · Insufficient Verification of Data Authenticity
Affects hickory-dnsSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 0.26.0-beta.1 when convenient.
Data as of 8 Nov 2026, 01:51 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.3 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 3.7 |
- Patch
- Available – fixed in 0.26.0-beta.1, 0.26.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/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.0-beta.1; hickory-dns to 0.26.2; hickory-dns to 0.26.2 or 0.26.0-beta.1.
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
A fix is available in hickory-proto version 0.26.0-beta.1 and hickory-net version 0.26.2. Users should upgrade to these versions or later to remediate the vulnerability.
Description
CVE-2026-123599 is a vulnerability in hickory-dns where DNSSEC validation can be bypassed due to improper handling of DNS class in verify_rrsets(). This allows attackers supplying DNS responses to forge certain DNS records, potentially authenticating any DNSKEY and forging child zone responses. The issue affects hickory-proto versions before 0.26.0-beta.1 and hickory-net versions before 0.26.2. A fix is available in versions 0.26.0-beta.1 and 0.26.2.