Hickory DNS through 0.25.0-alpha.3 DNSSEC Validation Bypass via RRSIG Signer's Name
Affects builds using the dnssec-ring or dnssec-aws-lc-rs feature with DNSSEC validation enabled, in hickory-proto through 0.25.0-alpha.3 and hickory-net 0.26.0-beta.1 through 0.26.1. 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
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Built with the dnssec-ring or dnssec-aws-lc-rs feature and configured to perform DNSSEC validation Affected hickory-proto versions 0.1 through 0.25.0-alpha.3; hickory-net versions v0.26.0-beta.1 through 0.26.1
- Published
- Last modified
- 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? →
- 17/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? →
- Specific setups only
- 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 0.1 through 0.25.0-alpha.3 and hickory-net before 0.26.2 contain a DNSSEC validation bypass because the validator verifies an RRSIG against the DNSKEY of whatever name appears in its Signer's Name field without checking that this name is the zone containing the RRset. Attackers controlling any secure zone can produce valid signatures over arbitrary records in unrelated zones, which resolvers, recursors, and clients using DnssecDnsHandle accept as authenticated.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- 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 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Built with the dnssec-ring or dnssec-aws-lc-rs feature and configured to perform DNSSEC validation Affected hickory-proto versions 0.1 through 0.25.0-alpha.3; hickory-net versions v0.26.0-beta.1 through 0.26.1Upgrade to a fixed version: 0.26.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- hickory-dns hickory-dns
From 0.1 · through 0.25.0-alpha.3
- 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-123605
Is CVE-2026-123605 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 party that controls a secure DNSSEC zone can produce valid signatures over records in unrelated zones. Resolvers, recursors and clients accept those records as authenticated.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-123605?
hickory-dns: from 0.1 through 0.25.0-alpha.3. 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?
Affected are hickory-proto 0.1 through 0.25.0-alpha.3 and hickory-net v0.26.0-beta.1 through 0.26.1, when built with the dnssec-ring or dnssec-aws-lc-rs feature and configured to perform DNSSEC validation. Check the hickory-proto or hickory-net version in your Cargo.lock and whether those features are enabled in your build.Source: github.com, vulncheck.com
How do I fix CVE-2026-123605?
Upgrade hickory-net to 0.26.2, the listed fixed version. Versions through 0.25.0-alpha.3 are covered by the same vulnerability entry.Source: github.com, vulncheck.com