Advisory

RUSTSEC-2026-0516

Also known as: CVE-2026-123586, GHSA-cx5j-p54p-q756, RUSTSEC-2026-0522

Summary

Recursor kept querying cyclic glueless sibling delegations

Details

Two 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.

Severity

Not rated by the source.

Dates

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

Affected packages and fixes

hickory-resolver

crates.io · All systems

Affected

  • introduced 0.26.0-beta.1, fixed 0.26.2 (semver)

Fixed versions

0.26.2

Fix

  • Fixed version 0.26.2
    cargo update -p hickory-resolver --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