Skip to main content
VulnerabilityPublished Updated

CVE-2026-123600: Hickory net · NSEC3 NODATA at a zone apex accepted without an NSEC3 record matching the query name

Affects hickory-netSource GCVE Database

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

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

Data as of 17 Nov 2026, 10:51 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
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 16 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 patch is available in Hickory net version 0.26.2 that corrects the validation logic to treat NSEC3 NODATA responses at the zone apex without a matching NSEC3 record as bogus. Users should upgrade to version 0.26.2 or later to remediate this vulnerability.

Description

A vulnerability in Hickory net's DNSSEC validation allows acceptance of a NSEC3 NODATA response at the zone apex without a matching NSEC3 record. This occurs because the validation skips the required check for the zone apex, potentially allowing an attacker who can modify DNS responses to replay signed records and cause a recursor to cache a false denial of existence for any record type at the apex.

References

Community reviews

Loading reviews…