Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

RRSIG signer name was not checked against the zone of the signed records

Historical advisory saved 12 Nov 2026 14:19:10 UTC. The publisher may have updated it since then. Latest advisory.

osv · RUSTSEC-2026-0507

Published

DNSSEC validation checked an RRset against the DNSKEYs of whatever zone was named in the RRSIG's Signer's Name field. RFC 4035 section 5.3.1 requires that name to be the zone that contains the RRset, but this was not checked. Anyone who controls a DNSSEC-signed zone, and can answer or modify DNS responses, can therefore sign records for names in an unrelated zone with their own keys and have the validator accept them as secure. This affects DNSSEC validation through `DnssecDnsHandle` (resolver, recursor and client) when built with `dnssec-ring` or `dnssec-aws-lc-rs`. The fix ignores an RRSIG whose signer name is not the RRset's owner name or one of its ancestors. It is in 0.26.2.

Source published
3 Sep 2026 12:00:00 UTC
Source modified
12 Nov 2026 14:00:04 UTC
Saved here
12 Nov 2026 14:19:10 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.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 08:58 UTC · 274 of 275 readable · 252 fully read · 18 waiting for GitHub's hourly limit · documentation 469/469 current