Read the docs

Hickory DNS DNSSEC validation accepts bogus wildcard responses

Priority LOW 27CWE-358Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
None · Low · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

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 is affected. The validator does not distinguish NODATA responses from positive responses expanded from wildcard records, a flaw classified under CWE-358. A remote attacker without privileges can combine an NSEC3 record matching the query name with a signed wildcard record into a bogus positive response that validation accepts, in a zone with wildcard records where NODATA is expected.

Written with Claude Haiku 5.5 from the sources below · 2026-11-08

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00218 12th percentileScored 2026-11-16
Fix Fixed hickory-dns (hickory-dns): 0.26.2

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
hickory-dnshickory-dns0.26.0-beta.1 to before 0.26.20.26.2Patch availableCNA
hickory-dnshickory-dnsup to 0.26.0-alpha.1—No fix listedCNA
  • hickory-dns Vendorhickory-dns Affected 0.26.0-beta.1 to before 0.26.2 Fixed in 0.26.2 Patch available CNA
  • hickory-dns Vendorhickory-dns Affected up to 0.26.0-alpha.1 Fixed in — No fix listed CNA

Remediation

Update hickory-net to version 0.26.2. The sources list no fixed version for hickory-proto.

Written with Claude Haiku 5.5 from the sources below · 2026-11-08

  • Fix · CNA hickory-dns (hickory-dns) Fixed in 0.26.2

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    hickory-dns 0.26.2

    36 records Highest priority Priority MEDIUM 12 MEDIUM, 24 LOW

    Other records, highest priority first

    • TI-2026-86748 Resource exhaustion in hickory-dns recursor via glueless NS referralsPriority MEDIUM 44
    • TI-2026-86746 Unbounded retry loop in Hickory DNS resolver enables resource exhaustionPriority MEDIUM 44
    • TI-2026-86730 Denial of service in Hickory DNS recursive resolver via empty poolPriority MEDIUM 44

Timeline

  1. 2026-11-08 Threatist record created from CVE-2026-123579
  2. 2026-11-08 Alias added: GHSA-xcqq-jfxv-w8jq
  3. 2026-11-09 Priority changed: MEDIUM → LOW
  4. 2026-11-13 CISA SSVC decision points changed

References

  • TI-2025-18857 DNSSEC validation may accept broken authentication chains CVSS 4.0MEDIUM 5.7
  • TI-2026-86750 CPU exhaustion in Hickory DNS hickory-proto via BinEncoder name compression CVSS 4.0HIGH 8.7
  • TI-2026-86749 Hickory DNS NSEC3 validation loop enables denial of service CVSS 4.0HIGH 8.7
  • TI-2026-86748 Resource exhaustion in hickory-dns recursor via glueless NS referrals CVSS 4.0HIGH 8.7
  • TI-2026-86746 Unbounded retry loop in Hickory DNS resolver enables resource exhaustion CVSS 4.0HIGH 8.7
  • TI-2026-86730 Denial of service in Hickory DNS recursive resolver via empty pool CVSS 4.0HIGH 8.7
See all 40 →

Sources