Skip to main content
VulnerabilityPublished

CVE-2026-123579: hickory-dns · Improperly Implemented Security Check for Standard

Affects hickory-dnsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 0.26.2 when convenient.

Data as of 8 Nov 2026, 02:03 UTC

CVSS 4.0 base score
6.3Medium
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.06.3
CNA (VulnCheck)CVSS 3.13.7
Patch
Available – fixed in 0.26.2
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/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-beta.1 <0.26.2
Fixed in
  • 0.26.2
hickory-dnshickory-dnsAffected
  • <=0.26.0-alpha.1
Fixed in–
crates.iohickory-dnspkg:cargo/hickory-dnsOther threatsAffected
  • >=0.26.0-beta.1 <0.26.2
  • <=0.26.0-alpha.1
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

A fix for this vulnerability is available in Hickory DNS version 0.26.2. Users should upgrade to version 0.26.2 or later to remediate this issue. No additional mitigation steps are indicated beyond applying the official patch.

Description

CVE-2026-123579 is a vulnerability in Hickory DNS affecting versions 0.26.0-beta.1 through before 0.26.2 and hickory-proto through 0.26.0-alpha.1. The DNSSEC validation does not properly distinguish between NODATA responses and wildcard-expanded positive responses. This flaw allows an attacker to craft a bogus positive DNS response by combining an NSEC3 record with a signed wildcard record, which the validation process incorrectly accepts.

References

Community reviews

Loading reviews…