Quick answers
- Is CVE-2026-123580 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123580 being exploited in the wild.
- How severe is CVE-2026-123580?
- High severity, with a CVSS score of 7.5, published 8 November 2026.
- Which products and versions are affected?
- Hickory-Dns Hickory-Net 0.26.0-beta.1 through 0.26.1; Hickory-Dns Hickory-Proto through 0.26.0-alpha.1.
- Is there a fix for CVE-2026-123580?
- Yes: fixed in hickory-net 0.26.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123580 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-123580?
- Check whether you run Hickory-Dns Hickory-Net or Hickory-Dns Hickory-Proto 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-net 0.26.2
Technical details
The vulnerability exists in DNSSEC NSEC3 record validation: the code compares only the hashed label of an NSEC3 record without verifying that the record belongs to the queried zone, allowing attackers to supply NSEC3 records from another zone with a matching hash to forge nonexistence proofs. This is an authentication bypass vulnerability requiring only network access and no user interaction. An attacker can manipulate DNSSEC responses to make valid domains appear nonexistent.
Affected products
- hickory-dns hickory-net 0.26.0-beta.1 through 0.26.1
- hickory-dns hickory-proto through 0.26.0-alpha.1
Timeline
- 2026-09-03: disclosed: GitHub security advisory published
- 2026-11-08: advisory: CVE-2026-123580 published