Skip to main content
CVE Radar
lowpublic exploit

CVE-2026-123598

CVE-2026-123598 — Hickory DNS 0.25.0 through 0.26.0-alpha.1 DNSSEC Bogus Answer Cache Poisoning

The validating recursor in Hickory DNS hickory-recursor 0.25.0 through 0.26.0-alpha.1, hickory-resolver 0.26.0-alpha.1 before 0.26.2, and hickory-net 0.26.0-beta.1 before 0.26.2 caches DNSSEC-bogus answers using the untrusted, attacker-supplied record TTL (capped at 24 hours) instead of a short validation-failure TTL. A remote attacker who spoofs a single authoritative response with an invalid signature and a long TTL can keep the bogus result cached for up to 24 hours.

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

5 products listed

CVSS base

3.7

low · 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.25.0 to <= 0.26.0-alpha.1Vulnerable
Hickory-Dnshickory-dns0.26.0-alpha.1 to < 0.26.2Vulnerable
Hickory-Dnshickory-dns0.26.2Patched
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

Low

Confidentiality

None

Integrity

None

Scope

Unchanged

Attack Complexity

High

Attack Vector

Network

Privileges Req

None

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
3.7CVSS 3.1low2.21.4NVD, hickory-dns (CNA), GHSA
6.3CVSS 4.0mediumn/an/ahickory-dns (CNA)

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

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-613 · Insufficient Session Expiration

  • Bypass Protection Mechanism::

Mitigation: Set sessions/credentials expiration date.::

Weakness & attack patterns

  • CWE-613

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 3.7 (AV:N)

    Nov 8, 2026 · NVD

  3. Initial · CVE published

    Nov 8, 2026 · NVD

  4. Added · GHSA-p25q-gxfm-cmhr published (medium)

    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-123598 is Hickory DNS 0.25.0 through 0.26.0-alpha.1 DNSSEC Bogus Answer Cache Poisoning, a low 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-123598. 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 3.7 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.