Advisory

RUSTSEC-2026-0520

Also known as: CVE-2026-123581, GHSA-929p-gjf6-5hqj, RUSTSEC-2026-0512

Summary

DNSSEC validation accepted a validly signed but unrelated RRset as the answer

Details

When a response had a non-empty answer section, DNSSEC validation treated it as a positive answer as long as the records in it validated. It did not check that any of those records had the queried name and either the queried type or type CNAME.

An attacker who can answer or modify DNS responses can therefore return a genuine, signed RRset for some other name or type, and have it accepted as a validated answer to the query instead of being handled as a response with no matching data.

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

The fix requires at least one answer record that matches the query name and is either of the queried type or a CNAME, both for positive responses and when NSEC records are checked. It is in 0.26.2.

Severity

Medium Basis: CVSS v3 score 5.3, vector CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Dates

Published
2026-09-03 12:00 UTC
Modified
2026-11-12 14:40 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