hickory-resolver: Resolver::lookup() and Resolver::lookup_ip() APIs obscure DNSSEC validation failures
When calling `Resolver::lookup()` or `Resolver::lookup_ip()` on a resolver with DNSSEC validation enabled, both methods return `Ok(...)` if DNSSEC validation fails. It is possible but very inconvenient to check the validation status of individual records. These methods should instead return an error when DNSSEC validation determines a response is bogus.
GHSA-5j98-2g5x-46v6
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: osv:GHSA-5j98-2g5x-46v6
hickory-resolver
Source reference: /affected/0/package/name
- Affected versions
- Not stated in this record
- Fixed versions
- 0.26.2
Source reference:
/affected/0/ranges - Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "0"
},
{
"fixed": "0.26.2"
}
]
}
],
"package": {
"name": "hickory-resolver",
"purl": "pkg:cargo/hickory-resolver",
"ecosystem": "crates.io"
},
"database_specific": {
"source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-5j98-2g5x-46v6/GHSA-5j98-2g5x-46v6.json"
}
}
]- Related CVEs
- CVE-2026-93657
Source reference:
/aliases
Publisher severity
high
Source reference: /database_specific/severity
- Event
- #85843 · Revision 1
- Added to Heist Feed
- Publisher date