Skip to main content
VulnerabilityPublished Updated

CVE-2026-123596: Hickory net · Parent-side NSEC at a zone cut accepted as proof of nonexistence below the cut

Affects hickory-netSource GCVE Database

0
Compare
Authoritative record:CVE-2026-123596· High 8.7

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

Data as of 13 Nov 2026, 13:12 UTC

CVSS 4.0 base score
8.7High
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.7
CNA (VulnCheck)CVSS 3.18.8
Patch
Available – fixed in 0.26.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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 13 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

Upgrade hickory-net to version 0.26.2 or later, where the vulnerability is fixed by improved DNSSEC validation logic. No other mitigation is required as the fix addresses the root cause directly.

Description

A vulnerability in hickory-net's DNSSEC validation allows an attacker who can modify DNS responses to replay parent zone NSEC records to cause a recursive resolver to accept a denial of existence (NXDOMAIN or NODATA) for valid names in a child zone. This occurs because the validation incorrectly treats parent-side NSEC records at a zone cut as proof of nonexistence below the cut, contrary to RFC 6840. The issue affects versions prior to 0.26.2 and is fixed in version 0.26.2.

References

Community reviews

Loading reviews…