# CVE-2026-123579: Hickory DNS 0.26.0-beta.1 before 0.26.2 DNSSEC Validation Bypass via Wildcard Expansion


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/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:** 8 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-123579, GHSA-vrv5-968r-5ggm, GHSA-xcqq-jfxv-w8jq, UBUNTU-CVE-2026-123579

## What is CVE-2026-123579?

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

### Official description

DNSSEC validation in Hickory DNS hickory-net 0.26.0-beta.1 before 0.26.2 and hickory-proto through 0.26.0-alpha.1 does not distinguish NODATA responses from wildcard-expanded positive responses. For a query that should return NODATA in a zone with wildcard records, an attacker can combine an NSEC3 record matching the query name with a signed wildcard record into a bogus positive response that validation accepts.

Weakness: CWE-358 (Improperly Implemented Security Check for Standard)

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


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

Upgrade to a fixed version.

## Is CVE-2026-123579 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123579 is a medium-severity vulnerability in hickory-dns, published on 8 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123579 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-123579/ (Markdown: https://insights.sbomify.com/CVE-2026-123579/index.md)
```

## Sources

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

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