Recursor kept querying cyclic glueless sibling delegations
Historical advisory saved 12 Nov 2026 15:18:33 UTC. The publisher may have updated it since then. Latest advisory.
osv · RUSTSEC-2026-0516
PublishedTwo zones can each delegate to name servers named only inside the other zone, with no glue records (the cyclic sibling case in RFC 9471 section 2.3). Such delegations can never be resolved, but the recursor did not stop when it came back to a zone it was already resolving. It kept sending queries until the per-request limits ran out, and zero TTLs on the referral NS records made this worse. Someone who controls two such zones can make a recursor send many upstream queries for each client query. This affects the recursive resolver, which is in hickory-resolver behind the opt-in `recursor` feature from 0.26.0-beta.1. Earlier releases shipped it as the separate hickory-recursor crate. From 0.26.2 each client request tracks the zones on its resolution stack and refuses to enter a zone that is already on it.
- Source published
- 3 Sep 2026 12:00:00 UTC
- Source modified
- 12 Nov 2026 14:40:46 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.