cve.bz

CVE-2026-123590 hickory-dns hickory-dns

6.3 mediumEPSS 0.2%

Medium (6.3) in hickory-dns hickory-dns. EPSS 0.2% 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 accept NSEC and NSEC3 records for DNSSEC nonexistence proofs when any other record with the same owner name passes signature validation. Attackers able to supply DNS responses can mix validly signed records with bogus same-name NSEC or NSEC3 records of different types in the authority section to forge nonexistence proofs.

Severity

CVSS 4.0

6.3 medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N

CVSS 3.1

4.8 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 5th 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: 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-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-123590 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123590?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123590?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-123590 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

CVE-2026-123590

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:

[![CVE-2026-123590](https://cve.bz/cve/badge/CVE-2026-123590.svg)](https://cve.bz/cve/CVE-2026-123590)

HTML:

<a href="https://cve.bz/cve/CVE-2026-123590"><img src="https://cve.bz/cve/badge/CVE-2026-123590.svg" alt="CVE-2026-123590"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
hickory-dnsfrom 0.26.0-beta.1 before 0.26.2
hickory-dnsthrough 0.26.0-alpha.1

Fix and patched versions

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13, 14rust-hickory-protono fix listedDEBIAN-CVE-2026-123590
Debian14rust-hickory-net0.26.3-1DEBIAN-CVE-2026-123590
Ubuntu24.04:LTS, 26.04:LTSrust-hickory-protono fix listedUBUNTU-CVE-2026-123590
Ubuntu26.10rust-hickory-net, rust-hickory-protono fix listedUBUNTU-CVE-2026-123590

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-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

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON