Skip to main content
Mallory
MediumVulnerability

CVE-2026-123600: DNSSEC NSEC3 NODATA Validation Bypass in Hickory DNS

Published Nov 8, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 2 in a dayToday
CVSS6.3Medium · v4
EPSS0.20%10th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-123600CWE-347

CVE-2026-123600 is a DNSSEC validation flaw in Hickory DNS affecting hickory-proto 0.25.0-alpha.3 through 0.25.2 and hickory-net 0.26.0-alpha.1 before 0.26.2. The DnssecDnsHandle implementation accepts NSEC3-signed NODATA responses for zone-apex queries as secure without requiring an NSEC3 record whose owner matches the hashed query name. The zone-apex validation path omits the required proof that the queried record type and CNAME are absent. An attacker able to supply or modify DNS responses can replay a genuinely signed non-apex NSEC3 record together with the zone's signed SOA record to create an authenticated false denial of an apex record.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises DNS response integrity by causing nonexistent-data responses for existing zone-apex records to be accepted as DNSSEC-secure and potentially returned with AD=1. Recursive resolvers can cache the false denial for the negative-cache TTL, disrupting services dependent on the denied apex record types. The demonstrated impact is false denial of records, not arbitrary positive-record substitution, code execution, or confidentiality loss.

Remediation

Patch, then assume compromise.

Upgrade to Hickory DNS releases 0.26.2 or later that perform DNSSEC validation through hickory-net. The fix in hickory-net 0.26.2 classifies improperly proven NSEC3 NODATA responses as bogus rather than secure. Applications using vulnerable hickory-proto validation directly or through hickory-resolver or hickory-recursor should migrate to the corrected validation implementation; no hickory-proto release containing a backported fix is identified.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-123600 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-123600 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-123600?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-123600.
Is there a patch for CVE-2026-123600?
Upgrade to Hickory DNS releases 0.26.2 or later that perform DNSSEC validation through hickory-net. The fix in hickory-net 0.26.2 classifies improperly proven NSEC3 NODATA responses as bogus rather than secure.
How severe is CVE-2026-123600?
CVE-2026-123600 has a CVSS v4 score of 6.3 (Medium) and an EPSS score of 0.20% (10th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
rustsecNews · Nov 17, 2026RUSTSEC-2026-0549: hickory-proto: NSEC3 NODATA at a zone apex accepted without an NSEC3 record matching the query name (hickory-proto) › RustSec Advisory DatabaseA DNSSEC validation flaw allows an attacker who can answer or modify DNS responses to replay genuine signed NSEC3 and SOA records and have a false denial of any record type at the zone apex accepted as secure. It affects hickory-proto 0.25.0-alpha.3 through 0.26.0-alpha.1, including use through hickory-resolver or hickory-recursor. No hickory-proto release contains a fix; users should migrate to releases 0.26.2 or later, which validate through hickory-net, where the flaw was fixed in 0.26.2.Read more ↗rustsecNews · Nov 17, 2026RUSTSEC-2026-0556: hickory-net: NSEC3 NODATA at a zone apex accepted without an NSEC3 record matching the query name › RustSec Advisory DatabaseA DNSSEC validation flaw in hickory-net allows an attacker able to answer or modify DNS responses to replay genuine signed NSEC3 and SOA records and have a false NODATA response for any record type at the zone apex accepted as secure. A recursive resolver can cache this denial for the negative TTL. The flaw affects validation through DnssecDnsHandle when built with dnssec-ring or dnssec-aws-lc-rs. Versions 0.26.2 and later are patched to treat these responses as bogus.Read more ↗tenable nessus pluginsNews · Nov 9, 2026Linux Distros Unpatched Vulnerability : CVE-2026-123600 | Tenable®A DNSSEC validation flaw in Hickory DNS allows on-path attackers or malicious authoritative servers to replay a validly signed non-apex NSEC3 record with the zone's signed SOA. This can cause an authenticated denial of any zone-apex resource-record type for the negative-cache TTL, affecting DNS integrity and availability. The advisory reports no vendor-supplied patch for the flagged distribution packages and no known solution.Read more ↗ghsa syntheticNews · Nov 8, 2026GHSA-qjhc-4gx4-vvmfA DNSSEC validation flaw in Hickory DNS allows zone-apex NODATA responses to be accepted as secure without an NSEC3 record matching the hashed query name. On-path attackers or malicious authoritative servers can replay a validly signed non-apex NSEC3 record together with the zone's signed SOA to produce an authenticated denial of any apex record type for the negative-cache TTL. Affected versions are hickory-proto 0.25.0-alpha.3 through 0.25.2 and hickory-net from 0.26.0-alpha.1 to versions before 0.26.2.Read more ↗
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.