Skip to main content
CVE Radar
highpublic exploit

CVE-2026-123605

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

Hickory DNS hickory-proto 0.1 through 0.25.0-alpha.3 and hickory-net before 0.26.2 contain a DNSSEC validation bypass because the validator verifies an RRSIG against the DNSKEY of whatever name appears in its Signer's Name field without checking that this name is the zone containing the RRset. Attackers controlling any secure zone can produce valid signatures over arbitrary records in unrelated zones, which resolvers, recursors, and clients using DnssecDnsHandle accept as authenticated.

Published Updated Sources: NVD, hickory-dns (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Public exploit

exploit code published, no use observed

EPSS

0%

ahead of 0% of scored CVEs

Affects

Hickory-Dns

3 products listed

CVSS base

8.8

high · 2 sources

Remediation

The vendor's own words where we have them.

Upgrade Hickory-dns to a fixed release (0.26.2). Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Prioritize based on EPSS, PoC availability, and external exposure.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Affected vendors, products and versions
VendorProductVersionsStatus
Hickory-Dnshickory-dns0.1 to <= 0.25.0-alpha.3Vulnerable
Hickory-Dnshickory-dns0.26.0-beta.1 to < 0.26.2Vulnerable
Hickory-Dnshickory-dns0.26.2Patched

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Every CVSS base score collected, by source and version
ScoreVersionSeverityExpl.ImpactSource
8.8CVSS 3.1high2.85.9NVD, hickory-dns (CNA), GHSA
8.7CVSS 4.0highn/an/ahickory-dns (CNA)

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-347 · Improper Verification of Cryptographic Signature

  • Gain Privileges or Assume Identity
  • Modify Application Data
  • Execute Unauthorized Code or Commands

Weakness & attack patterns

  • CWE-347

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-463 · Padding Oracle Crypto AttackCAPEC-475 · Signature Spoofing by Improper Validation

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

PoC repos

1

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Prioritize edge telemetry for network-reachable Hickory-dns.
  • Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.
web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026
  2. Added · CVSS 3.1 8.8 (AV:N)

    Nov 8, 2026 · NVD

  3. Initial · CVE published

    Nov 8, 2026 · NVD

  4. Added · GHSA-h7hc-rhv6-hvw6 published (high)

    Nov 8, 2026 · GitHub Security Advisory

  5. CVE published by MITRE.

    Nov 8, 2026 · SOCRadar CTI

References

4 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2026-123605 is Hickory DNS through 0.25.0-alpha.3 DNSSEC Validation Bypass via RRSIG Signer's Name, a high vulnerability affecting Hickory-dns from Hickory-dns. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-123605. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 8.8 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.