hickory-resolver has 3 CVEs on record. 3 were published in the last 90 days. The busiest recent month was October 2026 with 3. The median CVSS is 7.5 (high).
CVEs per month
Last 12 months, by publish date
1125/111225/120126/010226/020326/030426/040526/050626/060726/070826/080926/091026/10
- Exploited share
- 0% vs 1% corpus
- Median CVSS
- 7.5
- Publish → KEV
- —
- Last 90 days
- 3 prev 0
3
Total CVEs
0
Critical
0
CISA KEV
0
Exploited
Worst active — by depth score
GHSA-6w6g-hm98-mhgmHighhickory-resolver: Unbounded TC-retry loop in `NameServerPool::try_send` (resource-exhaustion DoS)41GHSA-5j98-2g5x-46v6High· 7.5hickory-resolver: Resolver::lookup() and Resolver::lookup_ip() APIs obscure DNSSEC validation failures41GHSA-6f2x-v7q7-m7m5Mediumhickory-resolver follows irrelevant CNAME records28
hickory-resolver vulnerabilities
CVEs affecting hickory-resolver, newest first. Open any entry for full detail, references, and exploit status.
3 CVEsRSS
GHSA-6w6g-hm98-mhgmHighhickory-resolver: Unbounded TC-retry loop in `NameServerPool::try_send` (resource-exhaustion DoS)
hickory-resolver: Unbounded TC-retry loop in `NameServerPool::try_send` (resource-exhaustion DoS)
▾ Twilighthickory-resolver · hickory-resolvervia GHSA
GHSA-5j98-2g5x-46v6High· 7.5hickory-resolver: Resolver::lookup() and Resolver::lookup_ip() APIs obscure DNSSEC validation failures
hickory-resolver: Resolver::lookup() and Resolver::lookup_ip() APIs obscure DNSSEC validation failures
▾ Twilighthickory-resolver · hickory-resolvervia GHSA
GHSA-6f2x-v7q7-m7m5Mediumhickory-resolver follows irrelevant CNAME records
hickory-resolver follows irrelevant CNAME records
▾ Sunlithickory-resolver · hickory-resolvervia GHSA