Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Hickory DNS 0.26.0-beta.1 before 0.26.2 DNSSEC Validation Bypass via Name Hash Collision

CVSS 4.0 8.2 HIGHCVSS 3.1 5.9 MEDIUMCheck source for fixed versionsKEV status unknown

Historical advisory recorded 12 Nov 2026 15:16:18 UTC. Read the latest advisory.

cve-program · CVE-2026-123592

Published

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.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-123592

Published

hickory-dns

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "hickory-dns",
                    "product": "hickory-dns",
                    "defaultStatus": "unaffected",
                    "packageURL": "pkg:cargo/hickory-net",
                    "versions": [
                        {
                            "version": "0.26.0-beta.1",
                            "status": "affected",
                            "versionType": "semver",
                            "lessThan": "0.26.2"
                        },
                        {
                            "version": "0.26.2",
                            "status": "unaffected",
                            "versionType": "semver"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 17 Nov 01:43 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current