Hickory-DNS 0.26.0-beta.1 before 0.26.2 DNSSEC Nonexistence Proof Forgery via NSEC3
Affects hickory-net 0.26.0-beta.1 through 0.26.1 and hickory-proto up to and including 0.26.0-alpha.1 where DNSSEC verification is performed. Fixed in hickory-net 0.26.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.26.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.26.2.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.26% · 17th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Hickory DNS hickory-net 0.26.0-beta.1 before 0.26.2 and hickory-proto through 0.26.0-alpha.1 perform insufficient checks on NSEC3 record names during DNSSEC verification, comparing only the hashed label without confirming the record belongs to the correct zone. Attackers can supply NSEC3 records from another zone with a matching hash label to forge DNSSEC nonexistence proofs.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.26.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- hickory-dns hickory-dns
From 0.26.0-beta.1 · fixed in 0.26.2
- hickory-dns hickory-dns
through 0.26.0-alpha.1
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123580
Is CVE-2026-123580 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
DNSSEC verification does not check the names on NSEC3 records thoroughly. An attacker can supply NSEC3 records from another zone with a matching hash label, which forges a DNSSEC nonexistence proof and loses data integrity.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-123580?
hickory-dns: from 0.26.0-beta.1 before 0.26.2. hickory-dns: through 0.26.0-alpha.1.Source: cve.now feed data
Am I affected, and how do I check?
hickory-net versions 0.26.0-beta.1 through 0.26.1 are affected, and hickory-proto versions up to and including 0.26.0-alpha.1 are affected. Check the installed hickory-net or hickory-proto version, and whether the software performs DNSSEC verification.Source: github.com, vulncheck.com
How do I fix CVE-2026-123580?
Upgrade hickory-net to 0.26.2, the fixed version listed in the advisory.Source: github.com, vulncheck.com