Is CVE-2026-123581 exploited in the wild?

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

How severe is CVE-2026-123581?

Medium severity, with a CVSS score of 5.3, 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-123581?

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-123581 attacked?

It is attacked over the network.

Am I affected by CVE-2026-123581?

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-123581: Hickory DNS DNSSEC validation flaw in DNSSEC verification

CVE-2026-123581 · Severity: medium · CVSS 5.3 · Published 2026-11-08

Hickory DNS is a DNS resolver library written in Rust. A flaw in its DNSSEC validation allows attackers to forge DNS responses by providing any valid signed record, even if unrelated to the query, causing the resolver to accept them as authentic answers rather than rejecting them. This could lead to DNS cache poisoning or allowing clients to trust incorrect DNS data.

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

Quick answers

Is CVE-2026-123581 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-123581 being exploited in the wild.
How severe is CVE-2026-123581?: Medium severity, with a CVSS score of 5.3, 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-123581?: 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-123581 attacked?: It is attacked over the network.
Am I affected by CVE-2026-123581?: 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 DNSSEC validation logic for positive responses only checks that some valid RRset exists in the answer section, without verifying that the RRset matches the query. An attacker can supply a signed but unrelated RRset to make responses lacking matching records validate as positive answers instead of no-data responses. The vulnerability affects hickory-proto through 0.26.0-alpha.1 and hickory-net 0.26.0-beta.1 before 0.26.2; it requires only network access and no authentication.

Affected products

Hickory DNS hickory-proto through 0.26.0-alpha.1
Hickory DNS hickory-net 0.26.0-beta.1 before 0.26.2

Timeline

2026-09-03: disclosed: GitHub security advisory GHSA-929p-gjf6-5hqj published
2026-11-08: advisory: CVE-2026-123581 published on NVD

References

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