Skip to main content
Mallory
← Back to News
open-source-dependency-vulnerabilityinternet-facing-service-vulnerability

Hickory DNSSEC Flaw Allows Forged Zone-Apex NODATA Responses to Be Accepted as Secure

Vulnerability Disclosure · 3 sources · Updated 8h ago · First seen Nov 17, 2026

Hickory DNSSEC Flaw Allows Forged Zone-Apex NODATA Responses to Be Accepted as Secure

A DNSSEC validation vulnerability in Hickory, tracked as CVE-2026-123600, allows forged NODATA responses at a DNS zone apex to be accepted as secure. An attacker able to answer or modify DNS responses can replay genuine signed NSEC3 and SOA records from the zone without providing an NSEC3 record matching the hashed query name. A recursive resolver may then cache the false denial of record existence for the negative TTL, suppressing legitimate DNS answers. The affected validation branch treated a query-name match with the SOA name as sufficient proof despite the missing NSEC3 match.

The flaw affects hickory-proto versions 0.25.0-alpha.3 through 0.26.0-alpha.1 and the affected DnssecDnsHandle implementation in hickory-net when built with the dnssec-ring or dnssec-aws-lc-rs feature. DNSSEC validation moved from hickory-proto to hickory-net starting in 0.26.0-beta.1; no hickory-proto release contains a fix. Affected users, including applications validating through hickory-resolver or hickory-recursor, should migrate to 0.26.2 or later. The patch changes the invalid proof result from secure to bogus and adds a regression test rejecting an apex MX NODATA response whose NSEC3 record does not match the queried name.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

3 events · Sep 3, 2026 – Nov 17, 2026
  1. Nov 17, 202622h ago

    RustSec issues CVE-2026-123600 advisories for hickory-net and hickory-proto

    RustSec issued advisories disclosing the DNSSEC validation bypass and its potential to cause recursive resolvers to cache false denials for the negative TTL. The advisories identify hickory-net 0.26.2 and later as patched and direct affected hickory-proto users to migrate to releases using the corrected hickory-net validator.

    RUSTSEC-2026-0556: hickory-net: NSEC3 NODATA at a zone apex accepted without an NSEC3 record matching the query name › RustSec Advisory Database
  2. Sep 3, 20263mo ago

    Hickory DNSSEC NSEC3 validation vulnerability reported

    The vulnerability subsequently tracked as CVE-2026-123600 was reported. The flaw allows an attacker able to answer or modify DNS responses to replay signed NSEC3 and SOA records and have false denials of records at a zone apex accepted as secure.

    RUSTSEC-2026-0556: hickory-net: NSEC3 NODATA at a zone apex accepted without an NSEC3 record matching the query name › RustSec Advisory Database
  3. Reported May 7, 20266mo ago

    Hickory fixes acceptance of improperly proven apex NODATA responses

    Commit ffdfb29 changes DNSSEC validation to classify apex NODATA responses lacking an NSEC3 record matching the hashed query name as bogus rather than secure, and adds a regression test. The advisories identify hickory-net 0.26.2 as patched; no hickory-proto release contains the fix.

    net: reject apex NODATA without NSEC3 matching H(QNAME) · hickory-dns/hickory-dns@ffdfb29 · GitHub
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.