CVE-2026-123598
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-be…
Impact
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.
An attacker can exploit this over the network, without logging in, without any action by a user. Specific conditions have to be met, which makes an attack harder. If it succeeds: low risk of outages.
Affected products · Hickory-dns
| Product | Affected versions |
|---|---|
| Hickory-dns | from 0.25.0 through 0.26.0-alpha.1 from 0.26.0-alpha.1 before 0.26.2 from 0.26.0-beta.1 before 0.26.2 Version 0.25.0 ≤0.26.0-alpha.1 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-29q9-p769-j8gq
- https://www.vulncheck.com/advisories/hickory-dns-0.25.0-through-0.26.0-alpha.1-dnssec-bogus-answer-cache-poisoning
- https://github.com/advisories/GHSA-p25q-gxfm-cmhr
- https://nvd.nist.gov/vuln/detail/CVE-2026-123598