Skip to main content
VulnerabilityPublished

CVE-2026-123587: hickory-dns · Authentication Bypass by Spoofing

Affects hickory-dnsSource CVE Database V5

0
Compare

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

Data as of 8 Nov 2026, 02:02 UTC

CVSS 4.0 base score
8.9High
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.9
CNA (VulnCheck)CVSS 3.16.8
Patch
Available – fixed in 0.26.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/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 <0.26.2
Fixed in
  • 0.26.2
crates.iohickory-dnspkg:cargo/hickory-dnsOther threatsAffected
  • >=0.26.0 <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

A fix is available in Hickory DNS hickory-net crate version 0.26.2. Users should upgrade to version 0.26.2 or later to remediate this vulnerability. No additional mitigation steps are indicated.

Description

CVE-2026-123587 is a high-severity vulnerability in the Hickory DNS hickory-net crate versions 0.26.0 up to but not including 0.26.2. It involves an authentication bypass via spoofing in DNSSEC validation, where crafted responses can cause the software to incorrectly accept invalid SOA records. This allows attackers who can supply DNS responses to forge the nonexistence of any resource record set (RRset).

References

Community reviews

Loading reviews…