---
id: "CVE-2026-123598"
page: "https://infrastack.ai/live/CVE-2026-123598"
kind: "vulnerability"
aliases: ["CVE-2026-123598"]
title: "Hickory DNS: bogus DNSSEC answers cached for up to 24 hours"
severity: "medium"
cvss: 6.3
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["dns", "dnssec", "hickory-dns", "package", "rust"]
not_affected_if: ["managed-dns", "no-dnssec-validation", "system-resolver"]
published_at: "2026-11-08T02:16:54+00:00"
first_seen_at: "2026-11-08T02:21:13+00:00"
updated_at: "2026-11-08T02:24:56+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-123598", "first_seen_at": "2026-11-08T02:21:13+00:00"}]
exploit_sources: []
---

# Hickory DNS: bogus DNSSEC answers cached for up to 24 hours

Link for people: https://infrastack.ai/live/CVE-2026-123598 (this .md is for agents)

The validating DNS recursor in Hickory DNS caches DNSSEC-bogus answers using the attacker-supplied record TTL instead of a short failure TTL. A remote attacker who spoofs one authoritative response with an invalid signature and a long TTL can keep the bad result cached for up to 24 hours.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the version of hickory-recursor, hickory-resolver or hickory-net in your Cargo.lock, for example with `cargo tree -i hickory-resolver`
- Confirm whether the service runs the validating recursor with DNSSEC validation enabled

## Fix

- hickory-resolver and hickory-net: move to `0.26.2` or later
- hickory-recursor: the fixed version is not stated in the sources given; unknown

## Timeline

- 2026-11-08T02:21:13+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-123598

## Documents

- [advisory] Vendor advisory: github.com https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-29q9-p769-j8gq
- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/hickory-dns-0.25.0-through-0.26.0-alpha.1-dnssec-bogus-answer-cache-poisoning

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_