All reports
High

hickory-resolver: Unbounded TC-retry loop in `NameServerPool::try_send` (resource-exhaustion DoS)

Affected versions

Version ranges need review.

Rust / Cargohickory-resolver
Affected versions
>= 0.26.0-beta.1, < 0.26.2
Fixed version
0.26.2
Rust / Cargohickory-resolver
Affected versions
>=0.26.0-beta.1 <0.26.2
Fixed version
0.26.2

Exploitation

CVE-2026-123604

Probability of exploitation in the next 30 days: 0.34%

FIRST EPSS · 2026-11-20

Description

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

Links

Credits

  • qifan-sailboat