NetSight
medium6.3

CVE-2026-123598

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-be…

Impact

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.

An attacker can exploit this over the network, without logging in, without any action by a user. Specific conditions have to be met, which makes an attack harder. If it succeeds: low risk of outages.

Affected products · Hickory-dns

ProductAffected versions
Hickory-dns
from 0.25.0 through 0.26.0-alpha.1
from 0.26.0-alpha.1 before 0.26.2
from 0.26.0-beta.1 before 0.26.2
Version 0.25.0 ≤0.26.0-alpha.1

Weakness classification

References