Is CVE-2026-123600 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-123600 being exploited in the wild.

How severe is CVE-2026-123600?

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-alpha.1 through 0.26.1; Hickory-Dns Hickory-Proto 0.25.0-alpha.3 through 0.25.2.

Is there a fix for CVE-2026-123600?

Yes: fixed in hickory-proto 0.25.3; 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-123600 attacked?

It is attacked over the network or from the adjacent network, in a software library.

Am I affected by CVE-2026-123600?

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.

CVE-2026-123600: Hickory DNS DNSSEC validation bypass in NSEC3 NODATA

CVE-2026-123600 · Severity: medium · CVSS 4.8 · Published 2026-11-08

Hickory DNS is a DNS resolver library used in applications to perform secure DNS lookups. A flaw in its DNSSEC validation allows attackers on the network path or malicious DNS servers to forge authenticated denial-of-service responses that trick applications into blocking legitimate DNS queries. This could prevent users from accessing services by making the DNS resolver cache false negative responses as if they were cryptographically verified.

Technologies: Hickory-Dns Hickory-Net, Hickory-Dns Hickory-Proto. Vendors: Hickory-Dns.

Quick answers

Is CVE-2026-123600 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-123600 being exploited in the wild.
How severe is CVE-2026-123600?: 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-alpha.1 through 0.26.1; Hickory-Dns Hickory-Proto 0.25.0-alpha.3 through 0.25.2.
Is there a fix for CVE-2026-123600?: Yes: fixed in hickory-proto 0.25.3; 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-123600 attacked?: It is attacked over the network or from the adjacent network, in a software library.
Am I affected by CVE-2026-123600?: 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 0.25.3; hickory-net 0.26.2

Technical details

The vulnerability is an incomplete verification of DNSSEC NSEC3 records in DnssecDnsHandle, where NODATA responses for zone-apex queries are marked Proof::Secure without verifying the presence of an NSEC3 record with a hashed owner matching the queried name. An on-path attacker or compromised authoritative server can replay a validly-signed non-apex NSEC3 with the zone's signed SOA to cause the resolver to return authenticated (AD=1) denial responses. The issue affects hickory-proto 0.25.0-alpha.3 through 0.25.2 and hickory-net 0.26.0-alpha.1 through 0.26.1 when DNSSEC validation features are enabled.

Affected products

Hickory DNS hickory-proto 0.25.0-alpha.3 through 0.25.2
Hickory DNS hickory-net 0.26.0-alpha.1 through 0.26.1

Timeline

2026-09-03: disclosed: GitHub security advisory published
2026-11-08: advisory: NVD entry published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.