Hickory DNS's Record Cache Accepts AUTHORITY-Section NS from Sibling Zone via Parent-Pool Zone-Context Elevation

published 2026-04-26 6 mo ago modified 2026-10-26 13 d ago also GHSA-83hf-93m4-rgwq , EUVD-2026-25687

cvss: 4.0; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 5%
public exploits: 0; none known

Hickory DNS hickory-recursor 0.1 through 0.25.2 allows cross-zone poisoning because cached data is not directly associated with a query that triggered a response.

Patch / fix

fixed in 2

crates.io hickory-recursor 0.26.0
Hickory Project Hickory DNS 0.26

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 6 mo ago (2026-04-27)

Exploit prediction

0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	4.0	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
crates.io	hickory-recursor	>=0.24.0, <0.26.0 1 listed version	0.26.0

Affected products

Hickory Project Hickory DNS

Classification

Weakness

CWE-706 Use of Incorrectly-Resolved Name or Reference
CWE-345 Insufficient Verification of Data Authenticity

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary