Hickory DNS before 0.26.0-beta.1 DNSSEC Validation Bypass via Non-IN Class Records
- Exploited
- No known exploitation
- Fix
- Fixed in 0.26.0-beta.1, 0.26.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.26.0-beta.1, 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.12% · 1st 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? →
- 23/100 · provisional
- 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-proto before 0.26.0-beta.1 and hickory-net before 0.26.2 contain a DNSSEC validation bypass because verify_rrsets() ignores DNS class when partitioning RRsets, so non-IN records skip signature verification yet are marked secure when the IN records verify. Attackers able to supply DNS responses can include forged CH or HS class records, including DS records, to authenticate any DNSKEY and forge child zone responses.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.3/10CVSS 6.3
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.26.0-beta.1, 0.26.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- hickory-dns hickory-dns
fixed in 0.26.0-beta.1
- hickory-dns hickory-dns
From 0.26.0-beta.1 · fixed in 0.26.2
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-123599
Is CVE-2026-123599 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
Which versions are affected by CVE-2026-123599?
hickory-dns: before 0.26.0-beta.1. hickory-dns: from 0.26.0-beta.1 before 0.26.2.Source: cve.now feed data
How do I fix CVE-2026-123599?
Upgrade to a fixed version: 0.26.0-beta.1, 0.26.2.Source: cve.now feed data