RUSTSEC-2026-0549

Source
https://rustsec.org/advisories/RUSTSEC-2026-0549
Import Source
https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2026-0549.json
JSON Data
https://api.osv.dev/v1/vulns/RUSTSEC-2026-0549
Aliases
Published
2026-09-03T12:00:00Z
Modified
2026-11-17T10:25:34Z
Summary
NSEC3 NODATA at a zone apex accepted without an NSEC3 record matching the query name (hickory-proto)
Details

In hickory-proto 0.25.0-alpha.3 through 0.26.0-alpha.1, NSEC3 NODATA validation returned a secure result for a query at the zone apex even when no NSEC3 record in the response matched the hash of the query name, which RFC 5155 section 8.5 requires. Someone who can answer or modify DNS responses could replay any genuine signed NSEC3 record from the zone with the zone's signed SOA record and get a denial of any record type at the apex accepted as secure.

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 or 0.26.0-alpha.1 (directly or through hickory-resolver or hickory-recursor) should move to the 0.26.2 or later releases, which validate through hickory-net.

Database specific
{
    "license":  "CC0-1.0"
}
References

Affected packages

crates.io / hickory-proto

Package

Name
hickory-proto
View open source insights on deps.dev
Purl
pkg:cargo/hickory-proto

Affected ranges

Type
SEMVER
Events
Introduced
0.25.0-alpha.3
Fixed
0.26.0-beta.1

Ecosystem specific

{
    "affected_functions":  null,
    "affects":  {
        "arch":  [],
        "functions":  [],
        "os":  []
    }
}

Database specific

categories
[
    "privilege-escalation"
]
cvss
null
informational
null
source
"https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2026-0549.json"