DNSSEC validation accepted a validly signed but unrelated RRset as the answer
Historical advisory saved 12 Nov 2026 15:18:33 UTC. The publisher may have updated it since then. Latest advisory.
osv · RUSTSEC-2026-0520
PublishedWhen 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.
- Source published
- 3 Sep 2026 12:00:00 UTC
- Source modified
- 12 Nov 2026 14:40:54 UTC
- Saved here
- 12 Nov 2026 15:18:33 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N