Skip to main content
VulnerabilityPublished Updated

CVE-2026-123594: NXDOMAIN accepted for a proven empty non-terminal (hickory-proto)

Affects hickory-protoSource 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.0-beta.1 when convenient.

Data as of 12 Nov 2026, 15:47 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.0-beta.1
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-proto to 0.26.0-beta.1.

Affected software

ProductAffectedFixed in
crates.iohickory-protopkg:cargo/hickory-protoOther threatsAffected
  • >=0.0.0-0 <0.26.0-beta.1
Fixed in
  • 0.26.0-beta.1

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

AI-suggested

Users should upgrade to hickory-net version 0.26.2 or later, which contains the fix for this vulnerability. Since the fix is included starting with hickory-proto 0.26.0-beta.1 (which uses hickory-net 0.26.2+), upgrading to these or later versions will mitigate the issue. No other mitigations are indicated.

Description

A vulnerability in hickory-proto up to version 0.26.0-alpha.1 allows its DNSSEC NSEC validation to incorrectly accept NXDOMAIN responses as secure, even when the response proves the queried name exists as an empty non-terminal. This occurs because the NXDOMAIN response code is not signed, enabling an attacker who can modify DNS responses to convert a genuine signed NODATA response into an accepted NXDOMAIN. The issue was fixed in hickory-net 0.26.2, which is used from hickory-proto 0.26.0-beta.1 onward.

References

Community reviews

Loading reviews…