# CVE-2026-123580: Hickory-DNS 0.26.0-beta.1 before 0.26.2 DNSSEC Nonexistence Proof Forgery via NSEC3


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 8 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-123580, GHSA-p2jv-r3m3-7wf4, GHSA-wgx4-v7mx-crxr, RUSTSEC-2026-0505, RUSTSEC-2026-0509, UBUNTU-CVE-2026-123580

## What is CVE-2026-123580?

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

### Official description

Hickory DNS hickory-net 0.26.0-beta.1 before 0.26.2 and hickory-proto through 0.26.0-alpha.1 perform insufficient checks on NSEC3 record names during DNSSEC verification, comparing only the hashed label without confirming the record belongs to the correct zone. Attackers can supply NSEC3 records from another zone with a matching hash label to forge DNSSEC nonexistence proofs.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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

2 open source packages ship an affected version, including hickory-net and hickory-proto.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `hickory-net` | crates.io | From 0.0.0-0 | 0.26.2 |
| `hickory-proto` | crates.io | From 0.0.0-0 | 0.26.0-beta.1 |

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

Upgrade hickory-net to 0.26.2 or later.

## Is CVE-2026-123580 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- hickory-net (crates.io): affected from 0.0.0-0; fixed in 0.26.2
- hickory-proto (crates.io): affected from 0.0.0-0; fixed in 0.26.0-beta.1

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-123580/ (Markdown: https://insights.sbomify.com/CVE-2026-123580/index.md)
```

## Sources

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

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