CVSS 4.0
6.3 mediumCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:NCVE-2026-123594
Medium (6.3) in hickory-dns hickory-dns. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.
On this page
Hickory DNS hickory-proto through 0.26.0-alpha.1 and hickory-net 0.26.0-beta.1 before 0.26.2 contain an NSEC validation flaw that returns a secure proof for NXDOMAIN responses when the covering NSEC's Next Domain Name is a strict descendant of the query name, which actually proves the name exists as an empty non-terminal. On-path attackers can flip the unsigned rcode of a genuine signed NODATA response from NOERROR to NXDOMAIN, causing validators to accept forged nonexistence of the name.
Severity
CVSS 3.1
4.8 mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L- EPSS
- 0.1% estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-10. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-09. 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-345 Insufficient Verification of Data Authenticity
- OWASP Top 10
- A08:2025 Software or Data Integrity Failures
- Published
- Modified
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-123594 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123594?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123594?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-123594 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 | through 0.26.0-alpha.1 |
| hickory-dns | from 0.26.0-beta.1 before 0.26.2 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 13, 14 | rust-hickory-proto | no fix listed | DEBIAN-CVE-2026-123594 |
| Debian | 14 | rust-hickory-net | 0.26.3-1 | DEBIAN-CVE-2026-123594 |
| Ubuntu | 24.04:LTS, 26.04:LTS | rust-hickory-proto | no fix listed | UBUNTU-CVE-2026-123594 |
| Ubuntu | 26.10 | rust-hickory-net, rust-hickory-proto | no fix listed | UBUNTU-CVE-2026-123594 |
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)
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-345 (12).