CVE-2026-123598: hickory-dns · Insufficient Session Expiration
Affects hickory-dnsSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 0.26.2 when convenient.
Data as of 8 Nov 2026, 01:51 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.3 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 3.7 |
- Patch
- Available – fixed in 0.26.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.
What to do
Upgrade hickory-dns to 0.26.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| hickory-dnshickory-dns | Affected
| Fixed in– |
| hickory-dnshickory-dns | Affected
| Fixed in
|
| hickory-dnshickory-dns | Affected
| Fixed in
|
crates.iohickory-dnspkg:cargo/hickory-dnsOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade affected Hickory DNS components to version 0.26.2 or later, where the caching behavior for DNSSEC-bogus answers has been corrected to use a short validation-failure TTL instead of the attacker-supplied TTL. No other mitigation is indicated.
Description
CVE-2026-123598 is a vulnerability in Hickory DNS validating recursor components where DNSSEC-bogus answers are cached using the attacker-supplied TTL, allowing a remote attacker to keep invalid DNS responses cached for up to 24 hours. This affects versions from 0.25.0 through 0.26.0-alpha.1, 0.26.0-alpha.1 before 0.26.2, and 0.26.0-beta.1 before 0.26.2. The issue is fixed in version 0.26.2.