CVSS 4.0
8.7 highCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NCVE-2026-123605 hickory-dns hickory-dns
High (8.7) in hickory-dns hickory-dns. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in hickory-net 0.26.2.
On this page
Hickory DNS hickory-proto 0.1 through 0.25.0-alpha.3 and hickory-net before 0.26.2 contain a DNSSEC validation bypass because the validator verifies an RRSIG against the DNSKEY of whatever name appears in its Signer's Name field without checking that this name is the zone containing the RRset. Attackers controlling any secure zone can produce valid signatures over arbitrary records in unrelated zones, which resolvers, recursors, and clients using DnssecDnsHandle accept as authenticated.
Severity
CVSS 3.1
8.8 highCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H- EPSS
- 0.2% estimated probability of exploitation activity in the next 30 days; 15th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-347 Improper Verification of Cryptographic Signature
- OWASP Top 10
- A04:2025 Cryptographic Failures
- Published
- Modified
- Assigned by
- VulnCheck (CNA)
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-123605 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123605?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123605?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-123605 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-123605)
HTML:
<a href="https://cve.bz/cve/CVE-2026-123605"><img src="https://cve.bz/cve/badge/CVE-2026-123605.svg" alt="CVE-2026-123605"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| hickory-dns | from 0.1 through 0.25.0-alpha.3 |
| hickory-dns | from 0.26.0-beta.1 before 0.26.2 |
Fix and patched versions
hickory-net(crates.io): fixed in 0.26.2- Debian: fixed package versions per release
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| RUSTSEC-2026-0507 | crates.io | hickory-net | >=0.0.0-0 <0.26.2 | 0.26.2 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 13, 14 | rust-hickory-proto | no fix listed | DEBIAN-CVE-2026-123605 |
| Debian | 14 | rust-hickory-net | 0.26.3-1 | DEBIAN-CVE-2026-123605 |
| Ubuntu | 24.04:LTS, 26.04:LTS | rust-hickory-proto | no fix listed | UBUNTU-CVE-2026-123605 |
| Ubuntu | 26.10 | rust-hickory-net, rust-hickory-proto | no fix listed | UBUNTU-CVE-2026-123605 |
| Azure Linux | 3 | netavark | no fix listed | AZL-113224 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.
Attack patterns (CAPEC)
- CAPEC-463 Padding Oracle Crypto Attack Severity: High
- CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.
History
- The NVD deferred its analysis
Changes since this site first stored the record. The same for every record: /api/public/changes.