hickory-proto
Affected
- introduced
0.0.0-0, fixed0.26.0-beta.1(semver)
Fixed versions
0.26.0-beta.1
Fix
- Fixed version
0.26.0-beta.1cargo update -p hickory-proto --precise 0.26.0-beta.1
Advisory
Also known as: CVE-2026-123580, GHSA-p2jv-r3m3-7wf4, RUSTSEC-2026-0509
NSEC3 owner names not checked against the zone in DNSSEC validation (hickory-proto)
Up to 0.26.0-alpha.1, hickory-proto's DNSSEC validation matched NSEC3 records to a name only by the hashed first label of the NSEC3 owner name, without checking that the rest of the owner name was the zone in question. A signed NSEC3 record from any zone the attacker controls could therefore be used, by someone who can answer or modify DNS responses, to prove that a name in another zone does not exist.
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 older hickory-proto releases (directly or through hickory-resolver or hickory-recursor) should move to the 0.26.2 or later releases, which validate through hickory-net.
High Basis: CVSS v3 score 7.5, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
0.0.0-0, fixed 0.26.0-beta.1 (semver)0.26.0-beta.1
0.26.0-beta.1cargo update -p hickory-proto --precise 0.26.0-beta.1Fix 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