Skip to main content
VulnerabilityPublished

CVE-2026-123596: hickory-dns · Insufficient Verification of Data Authenticity

Affects hickory-dnsSource CVE Database V5

0
Compare

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

Data as of 8 Nov 2026, 02:02 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.18.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: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.2.

Affected software

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

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 the DNSSEC validation flaw in the NSEC handler is fixed. No other mitigation is required as the vulnerability is addressed by this official fix.

Description

CVE-2026-123596 is a high-severity vulnerability in hickory-dns affecting versions up to 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 NSEC handler that incorrectly accepts parent-side ancestor-delegation NSEC records as proof of nonexistence for names below the zone cut. This flaw allows an attacker capable of on-path interception, rogue parent nameserver control, or winning a port and TXID race to forge an NXDOMAIN response that causes authenticated denial of existing child-zone names cached for the negative TTL. The issue is fixed in version 0.26.2.

References

Community reviews

Loading reviews…