hickory-resolver before 0.26.2 DNSSEC Validation Bypass (CVE-2026-93657) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-93657

hickory-resolver before 0.26.2 DNSSEC Validation Bypass

Answer in brief

CVE-2026-93657 records a Unknown severity vulnerability in hickory-resolver before 0.26.2 DNSSEC Validation Bypass. The current sources do not mark it as known exploited. The current feed maps hickory-dns/hickory-resolver (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 18, 2026Updated Sep 18, 2026Source checked Sep 18, 2026First seen by HOL Sep 18, 2026Material review Sep 18, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps hickory-dns/hickory-resolver (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
hickory-dns/hickory-resolvergeneric	>=0 <0.26.2	0.26.2

Recommended response

Check inventory. Check lockfiles and deployed manifests for hickory-dns/hickory-resolver.
Review the reported fix. Update hickory-dns/hickory-resolver to 0.26.2 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 18, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 18, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 18, 2026

Sources and claim methodology

Upstream source description

hickory-resolver versions before 0.26.2 fail to propagate bogus DNSSEC proof states through the Resolver::lookup() and Resolver::lookup_ip() APIs, allowing invalid records to be returned as successful results. Attackers controlling the answering zone or positioned on the network path can have forged DNS records accepted as validated, bypassing DNSSEC authentication checks.

Quoted source text, attributed separately from HOL analysis.