hickory-net
Affected
- introduced
0.0.0-0, fixed0.26.2(semver)
Fixed versions
0.26.2
Fix
- Fixed version
0.26.2cargo update -p hickory-net --precise 0.26.2
Advisory
Also known as: CVE-2026-123600, GHSA-3jvh-8vj5-65rq, RUSTSEC-2026-0549
NSEC3 NODATA at a zone apex accepted without an NSEC3 record matching the query name
RFC 5155 section 8.5 says a NODATA response proven with NSEC3 needs an NSEC3 record whose hashed owner name equals the hash of the query name, and whose type bitmap has neither the query type nor CNAME.
NSEC3 NODATA validation skipped this when the query name was the zone apex (the SOA owner). If no NSEC3 record matched the query name, no closest encloser was found and no wildcard applied, it still returned a secure result.
An attacker who can answer or modify DNS responses can replay any genuine signed NSEC3 record from the zone together with the zone's signed SOA record, and get a NODATA answer for any record type at the apex accepted as secure. A recursor caches that denial for the negative TTL.
This affects DNSSEC validation through DnssecDnsHandle when built with dnssec-ring or dnssec-aws-lc-rs.
The fix treats such a response as bogus.
Not rated by the source.
0.0.0-0, fixed 0.26.2 (semver)0.26.2
0.26.2cargo update -p hickory-net --precise 0.26.2Fix 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
Source: RustSec Advisory Database · CC0-1.0