CVE-2026-123599: Records with a DNS class other than the query's marked secure without being validated (hickory-proto)
Affects hickory-protoSource GCVE Database
Not known to be exploited · CVSS 6.3 Medium : upgrade to 0.26.0-beta.1 when convenient.
Data as of 17 Nov 2026, 10: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.0-beta.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/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 16 Nov 2026.
What to do
Upgrade hickory-proto to 0.26.0-beta.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
crates.iohickory-protopkg:cargo/hickory-protoOther 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
Users should upgrade to hickory-net version 0.26.2 or later, where the DNSSEC validation issue is fixed. Since no hickory-proto release contains the fix, users relying on hickory-proto or dependent crates like hickory-resolver or hickory-recursor must ensure they use hickory-net 0.26.2 or newer for DNSSEC validation. Applying this update is the recommended remediation.
Description
A vulnerability in hickory-proto before version 0.26.0-beta.1 causes DNSSEC validation to incorrectly mark DNS records of classes other than IN as secure without proper validation. This allows an attacker capable of modifying DNS responses to inject forged records of other classes, including DS records, which are then accepted as validated.