Skip to main content
VulnerabilityPublished Updated

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

Affects hickory-netSource GCVE Database

0
Compare
Authoritative record:CVE-2026-123595· 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, which includes a fix that correctly validates NSEC3 records at zone cuts by verifying the type bitmap and rejecting inappropriate records as closest enclosers. No other mitigation is indicated by the vendor advisory.

Description

A vulnerability in Hickory net's DNSSEC validation allows acceptance of parent-side NSEC3 records at a zone cut as proof of nonexistence for names below the cut, which is incorrect according to RFC standards. This can lead to a recursor caching false negative DNS responses (NXDOMAIN or NODATA) for names below the delegation point. The issue affects versions before 0.26.2 and is fixed in version 0.26.2.

References

Community reviews

Loading reviews…