CVE-2026-123602 · Package
NO FIX YET · SEE WHAT TO DO
The Hickory DNS recursor reuses child-side apex NS records cached from zone queries, so stale records persist. An attacker who keeps querying a zone's NS records keeps retired name servers answering for that zone, the ghost domain name attack.
first public Sep 3, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Applications built on the Hickory DNS recursor (hickory-recursor, or hickory-resolver 0.26.0-beta.1 with the recursor feature enabled) can return answers from name servers the parent zone has revoked. Systems that use the default resolver configuration or do not enable the recursor feature are not described as affected. The sources do not say whether hickory-recursor has a fixed release.
Not affected if recursor-feature-disabled
Who cares dns, hickory-dns, recursor, rust
hickory-resolver or hickory-recursor version in your lockfile or Cargo.lockhickory-resolver 0.26.2 or later (fixed version for 0.26.0-beta.1 branch per the description)The Hickory DNS recursor in all versions of hickory-recursor and in hickory-resolver 0.26.0-beta.1 before 0.26.2 (recursor feature) is vulnerable to ghost domain names attacks because it reuses child-side apex NS RRsets cached from zone NS queries for iterative resolution. By repeatedly querying a zone's NS records, an attacker keeps the stale RRset cached indefinitely, letting name servers whose delegation the parent revoked keep answering for the zone.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.