Hickory DNS 0.26.0-beta.1 before 0.26.2 DNSSEC Validation Bypass via Name Hash Collision
Affects hickory-dns (hickory-net crate) versions 0.26.0-beta.1 through 0.26.1, where names differing only in dot positions can bypass DNSSEC validation. Fixed in 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.28% · 20th 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? →
- 25/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
The hickory-net crate in Hickory DNS 0.26.0-beta.1 before 0.26.2 allows DNSSEC validation bypass because Name's Hash ignores label lengths and ValidationCacheKey compares only that hash. An attacker controlling an unsigned delegation whose name differs from a signed target only in dot positions can prime an Insecure verdict, causing forged answers for the target to skip signature verification instead of returning SERVFAIL.
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.2/10CVSS 8.2
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 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
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-123592
Is CVE-2026-123592 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?
A name hash collision lets an attacker who controls an unsigned (Insecure) delegation use a name that differs from a signed target name only in dot positions. Forged answers for the signed target are then accepted without DNSSEC signature verification and returned as NOERROR with AD=0 instead of SERVFAIL.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-123592?
hickory-dns: from 0.26.0-beta.1 before 0.26.2.Source: cve.now feed data
Am I affected, and how do I check?
Hickory DNS hickory-net crate versions v0.26.0-beta.1 through v0.26.1 are affected. To check an installed version, look up the hickory-net crate version in use and compare it against that range.Source: github.com, vulncheck.com
How do I fix CVE-2026-123592?
Upgrade to hickory-dns 0.26.2, the first fixed version.Source: github.com, vulncheck.com