Quick answers
- Is CVE-2026-123590 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123590 being exploited in the wild.
- How severe is CVE-2026-123590?
- Medium severity, with a CVSS score of 4.8, published 8 November 2026.
- Which products and versions are affected?
- Hickory-Dns Hickory-Net 0.26.0-beta.1 before 0.26.2; Hickory-Dns Hickory-Proto through 0.26.0-alpha.1.
- Is there a fix for CVE-2026-123590?
- Yes: fixed in hickory-net 0.26.2; hickory-proto fix status unknown. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123590 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-123590?
- 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; hickory-proto fix status unknown
Technical details
The vulnerability exists in hickory-net and hickory-proto's DNSSEC validation logic: NSEC and NSEC3 records are accepted if any record with the same owner name passes signature validation, rather than validating each record's signature independently. An attacker with the ability to supply DNS responses can exploit this by including both valid and invalid records with the same name and different types in the authority section, causing bogus NSEC/NSEC3 records to be accepted for nonexistence proofs.
Affected products
- Hickory DNS hickory-net 0.26.0-beta.1 before 0.26.2
- Hickory DNS hickory-proto through 0.26.0-alpha.1
Timeline
- 2026-09-03: disclosed
- 2026-11-08: advisory