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, GHSA-6w6g-hm98-mhgm
Unbounded retries on truncated responses in the name server pool
When an upstream answer had the TC (truncated) bit set, the resolver's name server pool disabled UDP and sent the query again. It did this for every truncated answer, including answers that already came over TCP, and it kept no count of retries.
A name server that sets TC on every answer, which anyone running an authoritative server the resolver queries can do, kept each lookup re-sending queries over the same connection until the request deadline (5 seconds by default) ran out. This uses up resolver resources and sends many queries per lookup.
From 0.26.2 a truncated answer received after UDP has already been disabled ends the lookup with NetError::Truncated instead of retrying again.
Not rated by the source.
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: RustSec Advisory Database · CC0-1.0