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 NSEC3 Proof of Nonexistence Forgery

CVSS 4.0 8.3 HIGHCVSS 3.1 6.5 MEDIUMEUVD CVSS 4.0 8.3 CVSS 4.0 · [email protected] · Secondary 8.3 HIGHCVSS 3.1 · [email protected] · Secondary 6.5 MEDIUMosv · severity unknownFixed by hickory-proto 0.26.0-beta.1osv · severity unknownFixed by hickory-net 0.26.2KEV status unknown

cve-program · CVE-2026-123601

Published

Hickory DNS hickory-proto 0.25.0 through 0.26.0-alpha.1 and hickory-net 0.26.0-beta.1 before 0.26.2 invert the relational operators in the wrap-around branch of find_covering_record() in nsec3.rs, so the last NSEC3 record in a zone's hash ring covers every hash except its owner. Attackers able to inject DNS responses can replay that NSEC3 record and its RRSIG to forge DNSSEC-validated negative responses denying legitimate names.

Read the publisher's advisory

euvd · EUVD-2026-119360

Published

Hickory DNS hickory-proto 0.25.0 through 0.26.0-alpha.1 and hickory-net 0.26.0-beta.1 before 0.26.2 invert the relational operators in the wrap-around branch of find_covering_record() in nsec3.rs, so the last NSEC3 record in a zone's hash ring covers every hash except its owner. Attackers able to inject DNS responses can replay that NSEC3 record and its RRSIG to forge DNSSEC-validated negative responses denying legitimate names.

Read the publisher's advisory

nvd · CVE-2026-123601

Published

Hickory DNS hickory-proto 0.25.0 through 0.26.0-alpha.1 and hickory-net 0.26.0-beta.1 before 0.26.2 invert the relational operators in the wrap-around branch of find_covering_record() in nsec3.rs, so the last NSEC3 record in a zone's hash ring covers every hash except its owner. Attackers able to inject DNS responses can replay that NSEC3 record and its RRSIG to forge DNSSEC-validated negative responses denying legitimate names.

Read the publisher's advisory

osv · RUSTSEC-2026-0504

Published

In hickory-proto 0.25.0 through 0.26.0-alpha.1, DNSSEC validation handled the last NSEC3 record of a zone's hash chain with its two comparisons reversed. That record was treated as covering almost every hash it does not cover, so an attacker who can answer or modify DNS responses could replay it, with its RRSIG, to forge proofs that existing names have no records. From 0.26.0-beta.1 the DNSSEC validation code lives in the hickory-net crate, where this was fixed in hickory-net 0.26.2. No hickory-proto release contains a fix. Users of DNSSEC validation in hickory-proto 0.25 (directly or through hickory-resolver or hickory-recursor 0.25) should move to the 0.26.2 or later releases, which validate through hickory-net.

Read the publisher's advisory

osv · RUSTSEC-2026-0506

Published

When DNSSEC validation looks for the NSEC3 record that covers a hashed name, the last record in the zone's hash chain needs special handling, because its next hashed owner name sorts before its own hash. For that record the two comparisons were reversed: it was treated as covering every hash below its owner hash or above its next hash, which is mostly the part of the chain it does not cover. An attacker who can answer or modify DNS responses can replay that one signed NSEC3 record, with its RRSIG, from the target zone and use it in forged negative answers. The validator then accepts proof that names which do exist have no records. This affects DNSSEC validation through `DnssecDnsHandle` (resolver, recursor and client) when built with `dnssec-ring` or `dnssec-aws-lc-rs`. The same code was in hickory-proto before it moved to hickory-net. The fix corrects the comparison in `find_covering_record`. It is in 0.26.2.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-123601

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"
                        }
                    ]
                }

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-proto",
                    "versions": [
                        {
                            "version": "0.25.0",
                            "status": "affected",
                            "versionType": "semver",
                            "lessThanOrEqual": "0.26.0-alpha.1"
                        }
                    ]
                }

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

euvd · EUVD-2026-119360

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Nov 8, 2026, 1:38:29 AM

dateUpdated: Nov 10, 2026, 5:57:10 PM

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

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

nvd · CVE-2026-123601

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-480

Original publisher date fields

published: 2026-11-08T02:16:54.797

lastModified: 2026-11-10T22:15:59.797

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

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

osv · RUSTSEC-2026-0504

Published

hickory-proto

crates.io

SEMVER · introduced 0.25.0 → fixed 0.26.0-beta.1

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

osv · RUSTSEC-2026-0506

Published

hickory-net

crates.io

SEMVER · introduced 0.0.0-0 → fixed 0.26.2

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 18 Nov 19:58 UTC · 272 of 275 readable · 270 fully read · documentation 469/469 current