Advisory

RUSTSEC-2026-0509

Also known as: CVE-2026-123580, GHSA-p2jv-r3m3-7wf4, RUSTSEC-2026-0505

Summary

NSEC3 records from another zone were accepted in proofs of nonexistence

Details

When DNSSEC validation used NSEC3 records to prove that a name or record type does not exist, it compared only the hashed first label of each NSEC3 owner name with the hash of the name being checked. The rest of the owner name, which says which zone the record belongs to, was not checked.

Someone who controls any DNSSEC-signed zone can publish a signed NSEC3 record whose first label is the hash of a name in another zone. An attacker who can answer or modify DNS responses can then use it to make the validator accept that the name in the other zone does not exist.

This affects DNSSEC validation through DnssecDnsHandle when built with dnssec-ring or dnssec-aws-lc-rs.

The fix requires a matching NSEC3 record to belong to a zone that contains the checked name, and ignores NSEC3 records whose owner is not directly below the RRSIG signer name. It is in 0.26.2.

Severity

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

Dates

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

Affected packages and fixes

hickory-net

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.26.2 (semver)

Fixed versions

0.26.2

Fix

  • Fixed version 0.26.2
    cargo update -p hickory-net --precise 0.26.2

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