Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
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
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-11-08T01:38:16.186Z
Reserved: 2026-11-06T00:55:55.661Z
Link: CVE-2026-123582
No data.
Status : Received
Published: 2026-11-08T02:16:51.853
Modified: 2026-11-08T02:16:51.853
Link: CVE-2026-123582
No data.
OpenCVE Enrichment
Updated: 2026-11-08T03:30:15Z
-
CWE-345
Insufficient Verification of Data Authenticity