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-123605

Hickory DNS through 0.25.0-alpha.3 DNSSEC Validation Bypass via RRSIG Signer's Name

Products / packages hickory-dns · 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 · 8.7
Assessment vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
VulnCheck · CVSS:3.1 · 8.8
Assessment vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The headline uses the highest imported catalog score. Assessments can differ by source and CVSS version.

Severity

high8.8

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 1 of 1 mapped packages. Check each release branch and any separate product guidance.

What this means

Hickory DNS through 0.25.0-alpha.3 has a DNSSEC validation bypass via the RRSIG signer's name. An attacker with control over a DNSSEC-signed zone can sign records for unrelated zones. This affects DNSSEC validation in versions less than 0.26.2.

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

Attack conditions

RFC 4035 section 5.3.1 requires that name to be the zone that contains the RRset, but this was not checked.

Excerpt from the original source description below.

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.1 → through 0.25.0-alpha.3

custom 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-net crates.io
Affected range Recorded fix
From 0.0.0-0 before 0.26.2Semantic versions0.26.2

Version evidence: OSV · RUSTSEC-2026-0507

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

DNSSEC validation checked an RRset against the DNSKEYs of whatever zone was named in the RRSIG's Signer's Name field. RFC 4035 section 5.3.1 requires that name to be the zone that contains the RRset, but this was not checked.

Anyone who controls a DNSSEC-signed zone, and can answer or modify DNS responses, can therefore sign records for names in an unrelated zone with their own keys and have the validator accept them as secure.

This affects DNSSEC validation through DnssecDnsHandle (resolver, recursor and client) when built with dnssec-ring or dnssec-aws-lc-rs.

The fix ignores an RRSIG whose signer name is not the RRset's owner name or one of its ancestors. It is in 0.26.2.

References

5 sources
hickory-dns/hickory-dns · security/advisories/GHSA-2vgh-3wfw-qj7c
Vendor advisoryVulnCheck
www.vulncheck.com/advisories/hickory-dns-through-0.25.0-alpha.3-dnssec-validation-bypass-via-rrsig-signer-s-name
Security advisoryVulnCheck
crates.io/crates/hickory-net
Source reference
rustsec.org/advisories/RUSTSEC-2026-0507.html
Security advisory
hickory-dns/hickory-dns · commit 019535e
Patch

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-123605

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-347 ↗

Improper Verification of Cryptographic Signature

VulnCheck

Related →
Contributing organizations · 2
VulnCheck

Assigning organization

2026-11-08
CISA-ADP

Additional data publisher

2026-11-10

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-123605

    Observed 2026-11-10T18:16:46.903Z · upstream updated 2026-11-10T17:56:59.926Z

    Prioritization updated

    before

    []

    after

    [
  {
    "source": "CISA-ADP",
    "type": "SSVC",
    "role": "CISA Coordinator",
    "timestamp": "2026-11-10T16:26:03.880667Z",
    "decisions": [
      {
        "name": "Exploitation",
        "value": "none"
      },
      {
        "name": "Automatable",
        "value": "no"
      },
      {
        "name": "Technical Impact",
        "value": "total"
      }
    ]
  }
]

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

Showing up to 50 most recent observed changes.