Rust advisories / crate
Security history · hickory-resolver · data from Oct 24, 2026
Is hickory-resolver safe to use? Its security history
VerdictNo open advisories. 3 past vulnerabilities were fixed.
3advisories on record
3vulnerabilities
0unmaintained notices
nonenewest fixed version
Every advisory, newest first
- VulnerabilityGHSA-6f2x-v7q7-m7m5 · 2026-10-05hickory-resolver follows irrelevant CNAME records
- VulnerabilityGHSA-6w6g-hm98-mhgm · 2026-10-05hickory-resolver: Unbounded TC-retry loop in `NameServerPool::try_send` (resource-exhaustion DoS)
- VulnerabilityGHSA-5j98-2g5x-46v6 · 2026-10-05hickory-resolver: Resolver::lookup() and Resolver::lookup_ip() APIs obscure DNSSEC validation failures
Check your version
Run cargo tree -i hickory-resolver to see which version you build and why, or paste your Cargo.lock into the Cargo.toml checker to match every advisory against your exact versions.
Download trends, dependents and alternatives: hickory-resolver crate data.
RustSec advisories (CC0-1.0) and GitHub-reviewed advisories via OSV's crates.io export, downloaded Oct 24, 2026.
Up next
Before you depend on ithickory-resolver crate dataReal downloads, dependents and alternatives.Read it next →Did this answer your question?