cve.bz

CVE-2026-123581 hickory-dns hickory-dns

6.9 mediumEPSS 0.1%Fix available

Medium (6.9) in hickory-dns hickory-dns. EPSS 0.1% estimated probability of exploitation activity in the next 30 days. Fixed in hickory-proto 0.26.0-beta.1.

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 a DNSSEC validation flaw that accepts a response as a positive answer when any valid RRset appears in the answer section, without checking that the RRset is responsive to the query. Attackers can supply signed but unrelated RRsets so that responses lacking matching records are validated as positive answers instead of as no-data responses.

Severity

CVSS 4.0

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

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS
0.1% estimated probability of exploitation activity in the next 30 days; 2nd 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: yes · Technical impact: partial, 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-345 Insufficient Verification of Data Authenticity
OWASP Top 10
A08:2025 Software or Data Integrity 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 promptExplain CVE-2026-123581 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123581?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123581?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-123581 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-123581

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-123581](https://cve.bz/cve/badge/CVE-2026-123581.svg)](https://cve.bz/cve/CVE-2026-123581)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

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

Fix and patched versions

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
RUSTSEC-2026-0512crates.iohickory-proto>=0.0.0-0 <0.26.0-beta.10.26.0-beta.1
RUSTSEC-2026-0520crates.iohickory-net>=0.0.0-0 <0.26.20.26.2

Linux distributions

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

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)

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

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