CVSS 4.0
8.7 highCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NCVE-2026-123580
High (8.7) in hickory-dns hickory-dns. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
On this page
Hickory DNS hickory-net 0.26.0-beta.1 before 0.26.2 and hickory-proto through 0.26.0-alpha.1 perform insufficient checks on NSEC3 record names during DNSSEC verification, comparing only the hashed label without confirming the record belongs to the correct zone. Attackers can supply NSEC3 records from another zone with a matching hash label to forge DNSSEC nonexistence proofs.
Severity
CVSS 3.1
7.5 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N- EPSS
- 0.3% estimated probability of exploitation activity in the next 30 days; 17th percentile. Scored 2026-11-10. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-290 Authentication Bypass by Spoofing
- OWASP Top 10
- A07:2025 Authentication Failures
- Published
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-123580 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123580?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123580?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-123580 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.
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| hickory-dns | from 0.26.0-beta.1 before 0.26.2 |
| hickory-dns | through 0.26.0-alpha.1 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 13, 14 | rust-hickory-proto | no fix listed | DEBIAN-CVE-2026-123580 |
| Debian | 14 | rust-hickory-net | 0.26.3-1 | DEBIAN-CVE-2026-123580 |
| Ubuntu | 24.04:LTS, 26.04:LTS | rust-hickory-proto | no fix listed | UBUNTU-CVE-2026-123580 |
| Ubuntu | 26.10 | rust-hickory-net, rust-hickory-proto | no fix listed | UBUNTU-CVE-2026-123580 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.
Attack patterns (CAPEC)
- CAPEC-21 Exploitation of Trusted Identifiers Likelihood: High · Severity: High
- CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
- CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High
- CAPEC-60 Reusing Session IDs (aka Session Replay) Likelihood: High · Severity: High
- CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
- CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
- CAPEC-461 Web Services API Signature Forgery Leveraging Hash Function Extension Weakness Severity: High
- CAPEC-473 Signature Spoof
- CAPEC-476 Signature Spoofing by Misrepresentation Likelihood: Low · Severity: High
- CAPEC-667 Bluetooth Impersonation AttackS (BIAS) Likelihood: Medium · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.