Skip to main content
VulnerabilityPublished Updated

CVE-2026-42254: Hickory DNS · Use of Incorrectly-Resolved Name or Reference

Affects Hickory DNSSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.0 Medium : upgrade to 0.26 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
4.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.26
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Apr 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 30 Oct 2026.

What to do

Upgrade Hickory DNS to 0.26.

Affected software

ProductAffectedFixed in
Hickory ProjectHickory DNSAffected
  • >=0.1 <0.26
Fixed in
  • 0.26
GitHubhickory-dns/hickory-recursorpkg:github/hickory-dns/hickory-recursorOther threatsAffected
  • =0.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, cautious deployment and limiting exposure of vulnerable versions may reduce risk.

Description

Hickory DNS hickory-recursor 0.1 through 0.25.2 allows cross-zone poisoning because cached data is not directly associated with a query that triggered a response.

References

Community reviews

Loading reviews…