---
id: "CVE-2026-123592"
page: "https://infrastack.ai/live/CVE-2026-123592"
kind: "vulnerability"
aliases: ["CVE-2026-123592"]
title: "Hickory DNS: cache key flaw lets forged DNS answers skip DNSSEC checks"
severity: "high"
cvss: 8.2
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["dns-resolver", "dnssec", "hickory-dns", "package", "rust"]
not_affected_if: ["not-validating-resolver"]
published_at: "2026-11-08T02:16:53+00:00"
first_seen_at: "2026-11-08T02:21:13+00:00"
updated_at: "2026-11-08T02:23:16+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-123592", "first_seen_at": "2026-11-08T02:21:13+00:00"}]
exploit_sources: []
---

# Hickory DNS: cache key flaw lets forged DNS answers skip DNSSEC checks

Link for people: https://infrastack.ai/live/CVE-2026-123592 (this .md is for agents)

The hickory-net Rust crate in Hickory DNS 0.26.0-beta.1 mishandles its validation cache key, so names that differ only in dot positions can collide. An attacker controlling an unsigned delegation can make forged answers for a signed target skip signature verification.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the `hickory-net` version in `Cargo.lock` or `Cargo.toml`; versions below `0.26.2` in the 0.26 line are affected.
- Look for services that use Hickory DNS as a validating resolver.

## Fix

- `hickory-net` `0.26.2` or later (per the NVD description, fixed before `0.26.2`)

## Timeline

- 2026-11-08T02:21:13+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-123592

## Documents

- [advisory] Vendor advisory: github.com https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-rx82-4p2j-j5cv
- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/hickory-dns-0.26.0-beta.1-before-0.26.2-dnssec-validation-bypass-via-name-hash-collision

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_