All vulnerabilities
GHSA-5j98-2g5x-46v6CVE-2026-93657

hickory-resolver: Resolver::lookup() and Resolver::lookup_ip() APIs obscure DNSSEC validation failures

hickory-resolverrustLibraries & packages
Open in ThreatlineRecord JSON
CVSS
7.5High
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)No scoreNo FIRST EPSS score in this snapshot yet
Fixed in0.26.2Fixed versionGitHub
Published5 Oct 2026Updated 5 Oct 2026GitHub

What fixes it

  • 0.26.2hickory-resolver, rustGitHub
  • 0.26.2hickory-resolver, crates.ioOSVcargo update -p hickory-resolver --precise 0.26.2

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Description

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.

Text from GitHub Advisory Database

Affected versions 2

  • hickory-resolver, rust< 0.26.2GitHub
  • hickory-resolver, crates.iofrom first release, fixed in 0.26.2OSV

References 5