CVE-2026-123604
CVE-2026-123604 — Hickory DNS 0.26.0-beta.1 before 0.26.2 Resource Exhaustion DoS via NameServerPool::try_send TC-Retry Loop
Hickory DNS hickory-resolver 0.26.0-beta.1 before 0.26.2 contains an unbounded retry loop in NameServerPool::try_send, which re-queues truncated (TC) responses without checking the answering transport or counting iterations. A malicious authoritative server returning TC=1 on every transport keeps the resolver spinning on a persistent TCP connection until the 5-second request deadline expires, causing resource exhaustion.
Published Updated Sources: NVD, hickory-dns (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Public exploit
exploit code published, no use observed
EPSS
0%
ahead of 0% of scored CVEs
CVSS base
7.5
high · 2 sources
Remediation
The vendor's own words where we have them.
Upgrade Hickory-dns to a fixed release (0.26.2). Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Prioritize based on EPSS, PoC availability, and external exposure.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| Hickory-Dns | hickory-dns | 0.26.0-beta.1 to < 0.26.2 | Vulnerable |
| Hickory-Dns | hickory-dns | 0.26.2 | Patched |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Availability
High
Confidentiality
None
Integrity
None
Scope
Unchanged
Attack Complexity
Low
Attack Vector
Network
Privileges Req
None
User Interaction
None
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.1 | high | 3.9 | 3.6 | NVD, hickory-dns (CNA), GHSA |
| 8.7 | CVSS 4.0 | high | n/a | n/a | hickory-dns (CNA) |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
What this weakness leads to
MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.
CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')
- DoS: Resource Consumption (CPU)
- DoS: Resource Consumption (Memory)
- DoS: Amplification
Weakness & attack patterns
- CWE-835
Inferred from the weakness class — not observed against this CVE.
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
PoC repos
1
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Prioritize edge telemetry for network-reachable Hickory-dns.
- Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added · CVSS 3.1 7.5 (AV:N)
Nov 8, 2026 · NVD
Initial · CVE published
Nov 8, 2026 · NVD
Added · GHSA-9rhf-mg7m-qfr9 published (high)
Nov 8, 2026 · GitHub Security Advisory
CVE published by MITRE.
Nov 8, 2026 · SOCRadar CTI
References
4 on the record
- github.com/hickory-dns/hickory-dns/security/advisories/GHSA-6w6g-hm98-mhgm
Exploit, Third Party Advisory, Mitre, NIST
- www.vulncheck.com/advisories/hickory-dns-0.26.0-beta.1-before-0.26.2-resource-exhaustion-dos-via-nameserverpool-try-send-tc-retry-loop
Vendor Advisory, Mitre, NIST
- nvd.nist.gov/vuln/detail/CVE-2026-123604
NVD
- github.com/advisories/GHSA-9rhf-mg7m-qfr9
Exploit, Third Party Advisory
Elsewhere on this site
- Hickory-Dnsevery CVE for this vendor
- Denial of Servicesame class
- CWE-835other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2026-123604 is Hickory DNS 0.26.0-beta.1 before 0.26.2 Resource Exhaustion DoS via NameServerPool::try_send TC-Retry Loop, a high vulnerability affecting Hickory-dns from Hickory-dns. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-123604. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.5 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.