CVE-2026-123601

Hickory DNS 0.26.0-beta.1 before 0.26.2 NSEC3 Proof of Nonexistence Forgery

  • High 8.3

Description

Hickory DNS hickory-proto 0.25.0 through 0.26.0-alpha.1 and hickory-net 0.26.0-beta.1 before 0.26.2 invert the relational operators in the wrap-around branch of find_covering_record() in nsec3.rs, so the last NSEC3 record in a zone's hash ring covers every hash except its owner. Attackers able to inject DNS responses can replay that NSEC3 record and its RRSIG to forge DNSSEC-validated negative responses denying legitimate names.

Key facts

Published
8 Nov 2026
Last changed
10 Nov 2026
Assigned by
VulnCheck
EPSS
0.279% likely to be exploited in the next 30 days, higher than 20.66% of CVEs (scores for 15 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 8.3CVSS 4.0, Highfrom the CNA (VulnCheck)CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
  • 6.5CVSS 3.1, Mediumfrom the CNA (VulnCheck)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
hickory-dnshickory-dns
  • Default status: unaffected
  • 0.26.0-beta.1 up to but excluding 0.26.2 (affected)
  • 0.26.2 (unaffected)
hickory-dnshickory-dns
  • Default status: unaffected
  • 0.25.0 up to and including 0.26.0-alpha.1 (affected)

Timeline

  1. 8 Nov 2026 Published

Weakness

References