Advisory

RUSTSEC-2026-0550

Also known as: CVE-2026-123590, GHSA-57pw-897j-v4j6, RUSTSEC-2026-0557

Summary

Unsigned NSEC or NSEC3 record used in a nonexistence proof (hickory-proto)

Details

Up to 0.26.0-alpha.1, hickory-proto's DNSSEC validation kept an NSEC or NSEC3 record for a nonexistence proof if any authority record with the same owner name had validated, not only if that record itself had. Someone who can answer or modify DNS responses could pair a correctly signed record with a forged NSEC or NSEC3 record of the same owner name and get a forged denial 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 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.

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.0.0-0, 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