Quick answers
- Is CVE-2026-123605 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123605 being exploited in the wild.
- How severe is CVE-2026-123605?
- High severity, with a CVSS score of 8.8, 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 0.1 through 0.25.0-alpha.3.
- Is there a fix for CVE-2026-123605?
- Yes: fixed in hickory-proto: no patch (affected versions migrated to hickory-net); 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-123605 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-123605?
- 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-proto: no patch (affected versions migrated to hickory-net); hickory-net 0.26.2
Technical details
The validator verifies an RRSIG cryptographic signature against the DNSKEY of the name in the RRSIG's Signer's Name field without checking that this name is the zone containing the RRset (RFC 4035 §5.3.1 violation). An attacker controlling a secure zone can produce a valid RRSIG over arbitrary records in unrelated zones, bypassing DNSSEC validation. The flaw affects hickory-proto versions 0.1–0.25.0-alpha.3 and hickory-net versions 0.26.0-beta.1–0.26.1 when configured to perform DNSSEC validation.
Affected products
- Hickory DNS hickory-proto 0.1 through 0.25.0-alpha.3
- Hickory DNS hickory-net 0.26.0-beta.1 through 0.26.1
Timeline
- 2026-09-03: disclosed: GitHub Security Advisory published
- 2026-11-08: advisory: CVE-2026-123605 and NVD publication