hickory-resolver
Affected
- introduced
0.26.0-beta.1, fixed0.26.2(semver)
Fixed versions
0.26.2
Fix
- Fixed version
0.26.2cargo update -p hickory-resolver --precise 0.26.2
Advisory
Also known as: CVE-2026-123604, RUSTSEC-2026-0513
hickory-resolver: Unbounded TC-retry loop in NameServerPool::try_send (resource-exhaustion DoS)
When the hickory-resolver name server pool implementation receives an upstream response with the TC (truncated) header bit set, it re-queues the request to the same nameserver to retry with UDP transport disabled. However, the retry arm never inspects the transport that just answered and carries no iteration counter. An authoritative server that sets TC=1 on every available transport keeps the resolver spinning on one persistent TCP connection until the 5s per-request wall-clock deadline expires.
Reporter
Qifan Zhang, Palo Alto Networks
High Basis: The source's own band: HIGH
0.26.0-beta.1, fixed 0.26.2 (semver)0.26.2
0.26.2cargo update -p hickory-resolver --precise 0.26.2Fix 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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0