Skip to main content
VulnerabilityPublished Updated

CVE-2026-123604: Hickory resolver · Unbounded retries on truncated responses in the name server pool

Affects hickory-resolverSource GCVE Database

0
Compare
Authoritative record:CVE-2026-123604· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 0.26.2 soon.

Data as of 12 Nov 2026, 15:47 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.7
CNA (VulnCheck)CVSS 3.17.5
Patch
Available – fixed in 0.26.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.

What to do

Upgrade hickory-resolver to 0.26.2.

Affected software

ProductAffectedFixed in
crates.iohickory-resolverpkg:cargo/hickory-resolverOther threatsAffected
  • >=0.26.0-beta.1 <0.26.2
Fixed in
  • 0.26.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Hickory resolver to version 0.26.2 or later, where the retry logic on truncated responses has been corrected to prevent unbounded retries. No other mitigation is required as the fix is available and official.

Description

The Hickory resolver had an issue where it would endlessly retry DNS queries when receiving truncated (TC) responses from upstream name servers. This caused excessive resource usage and repeated queries until a default 5-second deadline expired. The problem was fixed in version 0.26.2 by stopping retries after receiving a truncated response once UDP was disabled.

References

Community reviews

Loading reviews…