CVE-2026-93657: hickory-resolver DNSSEC Validation Failure
Summary
CVE-2026-93657: hickory-resolver: Resolver::lookup() and Resolver::lookup_ip() APIs obscure DNSSEC validation failures. Affects hickory-resolver versions < 0.26.2. Fixed in 0.26.2. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
hickory-resolver is a Rust library designed for DNS resolution, providing APIs for looking up domain names and IP addresses. It supports DNSSEC validation to ensure the authenticity of DNS responses. However, a flaw in its implementation allows certain validation failures to go unnoticed, potentially leading to security risks.
Vulnerability Detail
The vulnerability arises from the behavior of the Resolver::lookup() and Resolver::lookup_ip() APIs when DNSSEC validation is enabled. Instead of returning an error when validation fails, these methods return Ok(...), obscuring the failure. This can mislead developers into believing that a DNS response is valid when it is not, exposing applications to potential attacks that exploit bogus DNS responses.
How To Fix
Latest published version: 0.26.3 as of 22 Oct 2026
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
0.26.2
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, developers can manually check the validation status of individual DNS records after calling the lookup methods. This can be cumbersome but ensures that bogus responses are identified. Example code snippet:
let result = resolver.lookup("example.com");
if let Ok(records) = result {
for record in records {
if !record.is_valid() {
// Handle invalid record
}
}
}
Conclusion
The hickory-resolver package has a critical vulnerability related to DNSSEC validation that can lead to accepting invalid DNS responses. It is crucial to update to the patched version 0.26.2 to mitigate this risk. Additionally, using tools like Vulert can help monitor and manage vulnerabilities effectively.
See every vulnerability recorded for hickory-resolver →
FAQ
The CVSS score of this vulnerability is 7.5, indicating a high severity level.
If your application uses hickory-resolver with DNSSEC validation, it may accept invalid DNS responses, leading to potential security breaches.
Yes, the vulnerability is fixed in version 0.26.2 of hickory-resolver. Updating to this version is recommended.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring an account.
Vulert monitors and alerts for open-source vulnerabilities in your software using just Cargo.lock, providing real-time insights into potential security risks.
References
Related vulnerabilities
Recent vulnerabilities recorded for hickory-resolver.