Rust hickory resolver: The validating recursor
Affects rust-hickory-resolverSource GCVE Database
Not known to be exploited · CVSS 6.3 Medium.
Data as of 18 Nov 2026, 15:20 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.3 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 3.7 |
| CNA | CVSS 4.0 | 6.3 |
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10rust-hickory-netpkg:deb/ubuntu/rust-hickory-net?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.10rust-hickory-recursorpkg:deb/ubuntu/rust-hickory-recursor?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.10rust-hickory-resolverpkg:deb/ubuntu/rust-hickory-resolver?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSrust-hickory-recursorpkg:deb/ubuntu/rust-hickory-recursor?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSrust-hickory-resolverpkg:deb/ubuntu/rust-hickory-resolver?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSrust-hickory-resolverpkg:deb/ubuntu/rust-hickory-resolver?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The validating recursor in Hickory DNS hickory-recursor 0.25.0 through 0.26.0-alpha.1, hickory-resolver 0.26.0-alpha.1 before 0.26.2, and hickory-net 0.26.0-beta.1 before 0.26.2 caches DNSSEC-bogus answers using the untrusted, attacker-supplied record TTL (capped at 24 hours) instead of a short validation-failure TTL. A remote attacker who spoofs a single authoritative response with an invalid signature and a long TTL can keep the bogus result cached for up to 24 hours.
References
- ubuntu.com/security/CVE-2026-123598 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-123598 (opens in a new tab)
- github.com/hickory-dns/hickory-dns/security/advisories/GHSA-29q9-p769-j8gq (opens in a new tab)
- vulncheck.com/advisories/hickory-dns-0.25.0-through-0.26.0-alpha.1-dnssec-bogus-answer-cache-poisoning (opens in a new tab)