Quick answers
- Is CVE-2026-123602 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123602 being exploited in the wild.
- How severe is CVE-2026-123602?
- Medium severity, with a CVSS score of 5.9, published 8 November 2026.
- Which products and versions are affected?
- Hickory-Dns Hickory-Recursor all versions; Hickory-Dns Hickory-Resolver 0.26.0-beta.1 before 0.26.2 (recursor feature).
- Is there a fix for CVE-2026-123602?
- Yes: fixed in hickory-resolver 0.26.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123602 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-123602?
- Check whether you run Hickory-Dns Hickory-Recursor or Hickory-Dns Hickory-Resolver at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: hickory-resolver 0.26.2
Technical details
The vulnerability is a cache poisoning flaw (CWE-672) in the DNS recursor's handling of child-side apex NS RRsets. When processing zone NS queries, the resolver caches the apex NS record set and reuses it for iterative resolution. An attacker can keep this RRset cached indefinitely through repeated queries, allowing revoked name servers to continue answering for a zone. This is a variant of CVE-2012-1033 and CVE-2022-30698.
Affected products
- Hickory DNS hickory-recursor all versions
- Hickory DNS hickory-resolver 0.26.0-beta.1 before 0.26.2 (recursor feature)
Timeline
- 2026-09-03: disclosed
- 2026-11-08: advisory