Description
The validating recursive resolver and validating forwarder in Hickory DNS (hickory-server) 0.25.0 before 0.26.2 do not check whether the SOA record passed DNSSEC validation when assembling NXDOMAIN or NODATA responses. An attacker able to supply forged DNS responses can have a forged SOA record returned to clients with the AD bit set, misleading clients that rely on the server's DNSSEC validation.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| hickory-dns | hickory-dns | 0.25.0 – < 0.26.2 | 0.26.2 |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 14 | rust-hickory-server | 0.26.3-1 | — |
| Debian 13 | rust-hickory-server | No fix yet | — |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 26.10 | rust-hickory-server | No fix yet | — |
| Ubuntu 26.04 LTS | rust-hickory-server | No fix yet | — |
References
- GitHub Security Advisory (GHSA-8hq4-5836-w6q4) vendor-advisory
- VulnCheck Advisory: Hickory DNS 0.25.0 before 0.26.2 DNSSEC Validation Bypass via SOA Record third-party-advisory