Hickory DNS 0.26.0-beta.1 before 0.26.2 DNSSEC Validation Bypass via Name Hash Collision
cve-program · CVE-2026-123592
PublishedThe 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.
Read the publisher's advisoryeuvd · EUVD-2026-119351
PublishedThe 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.
Read the publisher's advisorynvd · CVE-2026-123592
PublishedThe 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.
Read the publisher's advisoryosv · RUSTSEC-2026-0518
PublishedThe DNSSEC validation cache used a 64-bit hash of the query as its key, and two keys with the same hash counted as equal. The `Hash` implementation of `Name` hashed the bytes of the labels but not where one label ends and the next begins, so names that differ only in the placement of dots (such as `ab.c.` and `a.bc.`) hashed to the same value. An attacker who controls an unsigned delegation whose name collides in this way with a name in a signed zone can first get an Insecure result cached for their own name. A forged response for the signed name is then served from that cache entry without signature checks and returned with the AD bit clear, where validation should have failed. This affects DNSSEC validation through `DnssecDnsHandle` when built with `dnssec-ring` or `dnssec-aws-lc-rs`. The fix stores the query in the cache key and compares it on lookup. The `Hash` implementations of `Label`, `Name` and `LowerName` in hickory-proto were also changed to include label boundaries. Both are in 0.26.2.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-123592 · CVE overview and exploitation status
cve-program · CVE-2026-123592
- https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-rx82-4p2j-j5cv
- https://www.vulncheck.com/advisories/hickory-dns-0.26.0-beta.1-before-0.26.2-dnssec-validation-bypass-via-name-hash-collision
euvd · EUVD-2026-119351
- https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-rx82-4p2j-j5cv
- https://www.vulncheck.com/advisories/hickory-dns-0.26.0-beta.1-before-0.26.2-dnssec-validation-bypass-via-name-hash-collision
nvd · CVE-2026-123592
- https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-rx82-4p2j-j5cv
- https://www.vulncheck.com/advisories/hickory-dns-0.26.0-beta.1-before-0.26.2-dnssec-validation-bypass-via-name-hash-collision
osv · RUSTSEC-2026-0518
Related changes
Linked by CVE identifier- DNSSEC validation cache could reuse an Insecure result for a different name · Newly collected advisory · 12 Nov 2026
- Hickory DNS 0.26.0-beta.1 before 0.26.2 DNSSEC Validation Bypass via Name Hash Collision · Newly collected advisory · 8 Nov 2026