Skip to main content
VulnerabilityPublished Updated

CVE-2026-123592: Hickory net · DNSSEC validation cache could reuse an Insecure result for a different name

Affects hickory-netSource GCVE Database

0
Compare
Authoritative record:CVE-2026-123592· High 8.2

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

Data as of 12 Nov 2026, 15:36 UTC

CVSS 4.0 base score
8.2High
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.2
CNA (VulnCheck)CVSS 3.15.9
Patch
Available – fixed in 0.26.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/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. Users should upgrade to version 0.26.2 or later to ensure the DNSSEC validation cache correctly distinguishes DNS names and prevents reuse of insecure cache entries for different names. No additional mitigation is required once the update is applied.

Description

A DNSSEC validation cache vulnerability in hickory-net versions before 0.26.2 allows cache entries for insecure results to be reused for different DNS names due to a hash collision issue. This can cause forged DNS responses to be served without proper signature validation, bypassing DNSSEC protections. The issue is fixed in version 0.26.2 by improving cache key handling and hashing of DNS names.

References

Community reviews

Loading reviews…