Skip to main content
VulnerabilityPublished Updated

CVE-2026-123594: Hickory net · NXDOMAIN accepted for an empty non-terminal that the NSEC record proves exists

Affects hickory-netSource GCVE Database

0
Compare
Authoritative record:CVE-2026-123594· Medium 6.3

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

Data as of 12 Nov 2026, 15:36 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.14.8
CNACVSS 4.06.3
Patch
Available – fixed in 0.26.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/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 12 Nov 2026.

What to do

Upgrade hickory-net to 0.26.2.

Affected software

ProductAffectedFixed in
crates.iohickory-netpkg:cargo/hickory-netOther threatsAffected
  • >=0.0.0-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 net version 0.26.2, which rejects NXDOMAIN responses as invalid in the described scenario and properly validates NODATA responses. Users should upgrade to version 0.26.2 or later to remediate this vulnerability.

Description

A vulnerability in Hickory net's DNSSEC validation allows an attacker who can modify DNS responses to cause the validator to incorrectly accept an NXDOMAIN response for an existing empty non-terminal domain name. This occurs because the validator did not properly handle cases where the NSEC record's next domain name is lexically below the queried name, leading to acceptance of a forged NXDOMAIN response. The issue affects versions prior to 0.26.2 and has been fixed in version 0.26.2.

References

Community reviews

Loading reviews…