GHSA-vrv5-968r-5ggm: Hickory DNS 0.26.0-beta.1 before 0.26.2 DNSSEC Validation Bypass via Wildcard Expansion

Published Nov 8, 2026
·
Updated

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.

Event History

Nov 8, 2026
CVE Published
via OSV·01:38 AM
Data Sourced
via OSV·01:38 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which Hickory DNS components and versions are affected?

The issue affects hickory-net from 0.26.0-beta.1 before 0.26.2, and hickory-proto through 0.26.0-alpha.1.

2

What must an attacker provide to bypass validation?

The attacker must target a query that should produce NODATA in a zone containing wildcard records. They can combine an NSEC3 record matching the queried name with a signed wildcard record to create a bogus positive response accepted by validation.

3

What is the validation failure?

The affected validation logic does not distinguish a NODATA response from a positive response created through wildcard expansion. This allows the crafted wildcard-expanded response to be accepted as valid.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203