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.
CVE-2026-93657
HIGHPre-NVD 7.57.5—Trending — 3 sources updated this week
EchelonGraph scoreHIGH confidence
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-18. a secondary CVSS source baseline 7.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 38(Track)EG Risk 38/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 14%
- KEV
- Not listed
Published
September 18, 2026
Last Modified
September 18, 2026
Advisory Details (6)
Auto-updated Sep 18, 2026Patch available. Sources: github, github_commit, github_pr, github_release.
generic
hickory-resolver before 0.26.2 DNSSEC Validation Bypass | Advisories | VulnCheck
https://www.vulncheck.com/advisories/hickory-resolver-before-0.26.2-dnssec-validation-bypassgeneric
GitHub - hickory-dns/hickory-dns: A Rust based DNS client, server, and resolver · GitHub
https://github.com/hickory-dns/hickory-dnsgithub_release Patch Available
v0.26.2
Patch available: hickory-dns/hickory-dns v0.26.2
https://github.com/hickory-dns/hickory-dns/releases/tag/v0.26.2github_pr Patch Available
Security fixes (release/0.26, part 2)
Patch available: hickory-dns/hickory-dns v0.26.2 (PR #3871 merged 2026-09-03)
https://github.com/hickory-dns/hickory-dns/pull/3871github_commit
commit 30720f4fb22e (hickory-dns/hickory-dns)
Fix landed in hickory-dns/hickory-dns commit 30720f4fb22e — awaiting tagged release
https://github.com/hickory-dns/hickory-dns/commit/30720f4fb22e5556ecbf26d2c8274ea4a9fdd238github Patch Available
Resolver::lookup() and Resolver::lookup_ip() APIs obscure DNSSEC validation failures · Advisory · hickory-dns/hickory-dns · GitHub
https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-5j98-2g5x-46v6Vendor Advisories for CVE-2026-93657(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 13:57 UTCGHSA enrichment
- 2026-09-19 02:39 UTCEG score recompute
- 2026-09-19 02:39 UTCGHSA enrichment
- 2026-09-18 15:24 UTCEG score recompute
- 2026-09-18 14:34 UTCEG score recompute
- 2026-09-18 14:34 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-93657?
CVE-2026-93657 is a high vulnerability published on September 18, 2026. 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…
When was CVE-2026-93657 disclosed?
CVE-2026-93657 was first published in the National Vulnerability Database on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-93657 actively exploited?
CVE-2026-93657 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.8% of all scored CVEs.
What is the CVSS score of CVE-2026-93657?
CVE-2026-93657 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-93657?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-93657, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-93657
Is Your Infrastructure Affected by CVE-2026-93657?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.