Description
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: 2026-11-08
Score: 6.3 Medium
EPSS: n/a
KEV: No
Impact: Remote DNS Cache Poisoning
Action: Patch
AI Analysis

Impact

The vulnerability stems from the validating recursor in Hickory DNS, which incorrectly caches DNSSEC‑bogus answers using an attacker‑supplied record TTL capped at 24 hours instead of a short validation‑failure TTL. This flaw constitutes a CWE‑613 weakness. As a result, a remote attacker who spoofs a single authoritative response with an invalid signature and a long TTL can force the bogus result to be stored and used for up to 24 hours, allowing the attacker to redirect or intercept traffic through the recursor.

Affected Systems

Affected editions include hickory‑dns 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. These versions are distributed by the hickory‑dns project.

Risk and Exploitability

The CVSS score is 6.3, indicating a moderate impact. No EPSS score is available and the issue is not listed in the CISA KEV catalog, but its remote nature and lack of authentication requirements mean it can be successfully exploited in any environment that uses a vulnerable recursor. An attacker can craft a spoofed authoritative answer and inject a long TTL, causing the recursor to serve false data for a full day.

Generated by OpenCVE AI on November 8, 2026 at 03:10 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Hickory DNS to version 0.26.2 or newer, which fixes the caching logic for bogus DNSSEC answers.
  • If an upgrade cannot be performed immediately, temporarily disable DNSSEC validation in the recursor or set a short failure TTL to limit the duration of cached bogus data.
  • Implement monitoring for unexpected TTL values or DNSSEC failures in log data and review configurations to ensure only trusted authoritative servers are queried.

Generated by OpenCVE AI on November 8, 2026 at 03:10 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 08 Nov 2026 01:45:00 +0000

Type Values Removed Values Added
Description 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.
Title Hickory DNS 0.25.0 through 0.26.0-alpha.1 DNSSEC Bogus Answer Cache Poisoning
Weaknesses CWE-613
References
Metrics cvssV3_1

{'score': 3.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L'}

cvssV4_0

{'score': 6.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-11-08T01:38:27.111Z

Reserved: 2026-11-06T01:00:16.506Z

Link: CVE-2026-123598

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-08T02:16:54.327

Modified: 2026-11-08T02:16:54.327

Link: CVE-2026-123598

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-08T03:15:08Z

Weaknesses
  • CWE-613

    Insufficient Session Expiration