# CVE-2026-123582: Hickory DNS 0.25.0 before 0.26.2 DNSSEC Validation Bypass via SOA Record


- **Severity:** Medium 6.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 8 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-123582, GHSA-8hq4-5836-w6q4, GHSA-p5hq-5ppr-f8g2, UBUNTU-CVE-2026-123582

## What is CVE-2026-123582?

CVE-2026-123582 is a medium-severity vulnerability in hickory-dns, published on 8 Nov 2026. 

### Official 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.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-123582?


## How do I fix CVE-2026-123582?

Upgrade to a fixed version.

## Is CVE-2026-123582 being exploited?

There is no known exploitation of CVE-2026-123582 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123582 and fix it if it is affected.

What it is: CVE-2026-123582 is a medium-severity vulnerability in hickory-dns, published on 8 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123582 in the wild and no public exploit code.

Affected product: hickory-dns. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123582/ (Markdown: https://insights.sbomify.com/CVE-2026-123582/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123582
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123582
- OSV: https://osv.dev/vulnerability/CVE-2026-123582

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123582/
Summaries are generated and may contain mistakes; the official description above is the record.