Advisory

RUSTSEC-2026-0549

Also known as: CVE-2026-123600, GHSA-3jvh-8vj5-65rq, RUSTSEC-2026-0556

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.

Severity

Not rated by the source.

Dates

Published
2026-09-03 12:00 UTC
Modified
2026-11-17 10:25 UTC

Affected packages and fixes

hickory-proto

crates.io · All systems

Affected

  • introduced 0.25.0-alpha.3, fixed 0.26.0-beta.1 (semver)

Fixed versions

0.26.0-beta.1

Fix

  • Fixed version 0.26.0-beta.1
    cargo update -p hickory-proto --precise 0.26.0-beta.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences