CVE-2026-123591: Child-side NSEC or NSEC3 record accepted as proof that a delegation has no DS record (hickory-proto)
Affects hickory-protoSource GCVE Database
Not known to be exploited · CVSS 8.2 High : upgrade to 0.26.0-beta.1 soon.
Data as of 13 Nov 2026, 13:17 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.2 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 5.9 |
- Patch
- Available – fixed in 0.26.0-beta.1
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/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 13 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 fix is available starting with hickory-proto 0.26.0-beta.1 and hickory-net 0.26.2. Users should upgrade to these versions or later to ensure correct DNSSEC validation. No other mitigation is indicated by the vendor advisory.
Description
A vulnerability in hickory-proto versions before 0.26.0-beta.1 allows DNSSEC validation to incorrectly accept a child-side NSEC or NSEC3 record with the SOA bit set as proof that the parent zone lacks a DS record. This flaw could enable an attacker who can modify DNS responses to make a secure delegation appear insecure and forge records in the child zone. The issue was fixed by moving DNSSEC validation to the hickory-net crate, with the fix included starting in hickory-net 0.26.2. Users relying on older hickory-proto versions should upgrade to 0.26.0-beta.1 or later to mitigate this vulnerability.