Description
The validating recursive resolver and validating forwarder in Hickory DNS (hickory-server) 0.25.0 before 0.26.2 do not check whether the SOA record passed DNSSEC validation when assembling NXDOMAIN or NODATA responses. An attacker able to supply forged DNS responses can have a forged SOA record returned to clients with the AD bit set, misleading clients that rely on the server's DNSSEC validation.
Published: 2026-11-08
Score: 6.3 Medium
EPSS: n/a
KEV: No
Impact: DNSSEC Validation Bypass via forged SOA record
Action: Patch Immediately
AI Analysis

Impact

The vulnerable resolving and forwarding components of Hickory DNS do not verify that the SOA record they include in NXDOMAIN or NODATA responses actually passed DNSSEC validation, a flaw classified as CWE-345: Incorrect Validity Testing of an External Resource. An attacker who can inject forged DNS replies can cause the server to return a fabricated SOA record with the AD flag set, making clients believe the server has validated the data. This weakness allows an attacker to falsely claim DNSSEC authentication, potentially leading to mis‑trusted domain information or denial of service for clients relying on the server’s validation.

Affected Systems

The affected product is Hickory DNS (hickory-dns) version 0.25.0 through 0.26.1, before the patch was released in 0.26.2.

Risk and Exploitability

The vulnerability has a CVSS score of 6.3, indicating moderate severity, and there is no EPSS score available. It is not listed in the CISA KEV catalog. The likely attack vector is a remote network attacker who can send forged DNS responses to the vulnerable server; the attacker does not need local access but must target the server’s DNS port. Successful exploitation would allow the attacker to surface forged DNSSEC‑authenticated SOA records to clients.

Generated by OpenCVE AI on November 8, 2026 at 03:22 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Hickory DNS to version 0.26.2 or later.
  • Reconfigure client DNSSEC validation to ignore the AD flag from this server or enforce independent validation of the SOA record.
  • Continuously monitor DNS traffic for anomalous SOA records with the AD flag set and investigate any discrepancies.

Generated by OpenCVE AI on November 8, 2026 at 03:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 08 Nov 2026 01:45:00 +0000

Type Values Removed Values Added
Description The validating recursive resolver and validating forwarder in Hickory DNS (hickory-server) 0.25.0 before 0.26.2 do not check whether the SOA record passed DNSSEC validation when assembling NXDOMAIN or NODATA responses. An attacker able to supply forged DNS responses can have a forged SOA record returned to clients with the AD bit set, misleading clients that rely on the server's DNSSEC validation.
Title Hickory DNS 0.25.0 before 0.26.2 DNSSEC Validation Bypass via SOA Record
Weaknesses CWE-345
References
Metrics cvssV3_1

{'score': 3.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N'}

cvssV4_0

{'score': 6.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-11-08T01:38:16.186Z

Reserved: 2026-11-06T00:55:55.661Z

Link: CVE-2026-123582

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-08T02:16:51.853

Modified: 2026-11-08T02:16:51.853

Link: CVE-2026-123582

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-08T03:30:15Z

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity