Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.newCreate a CVE report
Check your stack
CVE-2026-123594

Hickory DNS through 0.26.0-alpha.1 DNSSEC NSEC Validation Bypass for Empty Non-Terminals

Products / packages hickory-dns · hickory-proto · hickory-net

Published

Share

Severity and exploitation

Not in CISA KEV

KEV coverage does not rule out exploitation.

KEV checked 15/11/2026, 01:10:30 UTC
VulnCheck · CVSS:4.0 · 6.3
Assessment vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N
VulnCheck · CVSS:3.1 · 4.8
Assessment vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
The headline uses the highest imported catalog score. Assessments can differ by source and CVSS version.

Severity

medium6.3

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Package fixes recorded

Fix versions are recorded for 2 of 2 mapped packages. Check each release branch and any separate product guidance.

What this means

Hickory DNS through 0.26.0-alpha.1 has a DNSSEC NSEC validation bypass for empty non-terminals, allowing an attacker who can modify DNS responses to turn a genuine signed NODATA response into an accepted NXDOMAIN. The weakness is due to insufficient verification of data authenticity. Affected versions are hickory-proto up to 0.26.0-alpha.1 and hickory-net before 0.26.2.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

hickory-dns · VulnCheck

hickory-dns

1 range
VulnCheck version evidence

Package identity

pkg:cargo/hickory-protoExplore hickory-proto →

Identity supplied by VulnCheck. Version matching requires compatible range evidence.

Compare with this publisher’s ranges. This does not inspect your installation.

affected

0 → through 0.26.0-alpha.1

semver versions

unaffected

unknown

Other versions: unaffected

hickory-dns · VulnCheck

hickory-dns

2 ranges
VulnCheck version evidence

Package identity

pkg:cargo/hickory-netExplore hickory-net →

Identity supplied by VulnCheck. Version matching requires compatible range evidence.

Compare with this publisher’s ranges. This does not inspect your installation.

affected

0.26.0-beta.1 → before 0.26.2

semver versions

unaffected

0.26.2

semver versions

unknown

Other versions: unaffected

Packages

Compare each installed version with the publisher’s affected ranges. Where a fix is recorded, choose the appropriate release branch and test compatibility before upgrading.

hickory-proto crates.io
Affected range Recorded fix
From 0.0.0-0 before 0.26.0-beta.1Semantic versions0.26.0-beta.1

Version evidence: OSV · RUSTSEC-2026-0511

View original version evidence (0 explicit versions)
hickory-net crates.io
Affected range Recorded fix
From 0.0.0-0 before 0.26.2Semantic versions0.26.2

Version evidence: OSV · RUSTSEC-2026-0519

View original version evidence (0 explicit versions)

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

Use the recorded fix for your release branch. Review the publisher’s instructions and test compatibility before upgrading.

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher description

Up to 0.26.0-alpha.1, hickory-proto's NSEC validation accepted an NXDOMAIN response as secure even when the covering NSEC record's next domain name was below the queried name, which proves the name exists as an empty non-terminal. Because the response code is not signed, someone who can modify DNS responses could turn a genuine signed NODATA response into an accepted NXDOMAIN.

From 0.26.0-beta.1 the DNSSEC validation code lives in the hickory-net crate, where this was fixed in hickory-net 0.26.2. No hickory-proto release contains a fix. Users of DNSSEC validation in older hickory-proto releases (directly or through hickory-resolver or hickory-recursor) should move to the 0.26.2 or later releases, which validate through hickory-net.

References

7 sources
hickory-dns/hickory-dns · security/advisories/GHSA-86vr-jm6c-7cpg
Vendor advisoryVulnCheck
www.vulncheck.com/advisories/hickory-dns-through-0.26.0-alpha.1-dnssec-nsec-validation-bypass-for-empty-non-terminals
Security advisoryVulnCheck
crates.io/crates/hickory-proto
Source reference
rustsec.org/advisories/RUSTSEC-2026-0511.html
Security advisory
hickory-dns/hickory-dns · commit bfbe7ed
Patch
crates.io/crates/hickory-net
Source reference
View 1 more references
rustsec.org/advisories/RUSTSEC-2026-0519.html
Security advisory

Inside the record

Evidence available

Package identity
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-123594

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-345 ↗

Insufficient Verification of Data Authenticity

VulnCheck

Related →
Contributing organizations · 2
VulnCheck

Assigning organization

2026-11-08
CISA-ADP

Additional data publisher

2026-11-09

Timeline

All times UTC

  1. Advisory published

    Publication date supplied by the source.

  2. Source updated

    Latest modification date supplied by the source.

  3. Last imported by cve.new

    Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes
  1. CVE · CVE-2026-123594

    Observed 2026-11-09T13:55:46.591Z · upstream updated 2026-11-09T13:51:34.546Z

    Prioritization updated

    before

    []

    after

    [
  {
    "source": "CISA-ADP",
    "type": "SSVC",
    "role": "CISA Coordinator",
    "timestamp": "2026-11-09T13:51:26.201045Z",
    "decisions": [
      {
        "name": "Exploitation",
        "value": "none"
      },
      {
        "name": "Automatable",
        "value": "no"
      },
      {
        "name": "Technical Impact",
        "value": "partial"
      }
    ]
  }
]

Large field values are marked as truncated previews. Original source snapshots remain retained.

Showing up to 50 most recent observed changes.