CVE-2026-123590: hickory-proto · Unsigned NSEC or NSEC3 record used
Affects hickory-protoSource GCVE Database
Not known to be exploited · CVSS 6.3 Medium : upgrade to 0.26.0-beta.1 when convenient.
Data as of 17 Nov 2026, 10:51 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.3 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 4.8 |
| CNA | CVSS 4.0 | 6.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:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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-proto to 0.26.0-beta.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
crates.iohickory-protopkg:cargo/hickory-protoOther threats | Affected
| Fixed in
|
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, which fixes the DNSSEC validation issue. Users of hickory-proto and related crates (hickory-resolver or hickory-recursor) should upgrade to hickory-net 0.26.2 or later. No hickory-proto release prior to 0.26.0-beta.1 contains the fix, so direct upgrades to hickory-net 0.26.2 or later are necessary. There is no indication that the vulnerability is mitigated by other means or that no action is required.
Description
A vulnerability in hickory-proto up to version 0.26.0-alpha.1 allows an attacker who can modify DNS responses to forge a denial of existence by pairing a correctly signed record with an unsigned NSEC or NSEC3 record. This occurs because the DNSSEC validation incorrectly accepts an NSEC or NSEC3 record for a nonexistence proof if any authority record with the same owner name validated, rather than requiring the NSEC/NSEC3 record itself to be validated. The issue was fixed in hickory-net 0.26.2, which is used starting from hickory-proto 0.26.0-beta.1. Users should upgrade to hickory-net 0.26.2 or later to mitigate this vulnerability.