CVE-2026-123596 — Hickory-Dns
HIGHCVE-2026-123596 is a high-severity (CVSS 8.8) CWE-345 vulnerability in hickory-dns hickory-dns. A fix is available — see the affected versions and patch details below.
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 in the validating recursor's NSEC handler that accepts…
Description
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 in the validating recursor's NSEC handler that accepts parent-side ancestor-delegation NSEC records as proof of nonexistence for names below the zone cut. An on-path attacker, rogue parent nameserver, or attacker winning a port and TXID race can deliver one forged NXDOMAIN response built from genuinely signed parent NSEC records, causing authenticated denial of existing child-zone names cached for the negative TTL.
Affected Products
hickory-dnshickory-dnshickory-dnshickory-dnsDetection & mitigation playbook
Vendor / applianceDetect
Inventory every hickory-dns hickory-dns deployment and check each version against the affected-products list above.
Fix
Apply the hickory-dns hickory-dns security patch or hotfix for CVE-2026-123596 on the affected version, following the vendor advisory for your exact build.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.
Frequently Asked Questions
Is CVE-2026-123596 being exploited in your environment?
Detect and block the exploit chain at execution, on systems you cannot patch yet.