Bug 2568727 (CVE-2026-123593)

Summary: CVE-2026-123593 hickory-net: hickory-proto: Hickory DNS: DNSSEC validation bypass via improper DNSKEY record name validation
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: dbosanac, jcantril, jlanda, jreimann, kshier, mdessi, mrizzi, pcattana, rbobbitt, rhel-process-autobot, rojacob, simaishi, stcannon, watson-tool-maintainers, yguenane
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in Hickory DNS. The DNSSEC (Domain Name System Security Extensions) validation mechanism compares public keys against configured trust anchors without checking the DNSKEY record name, allowing record sets containing trusted keys to be accepted without digital signature verification. A remote attacker capable of spoofing or controlling name server responses can exploit this vulnerability to bypass DNSSEC validation and inject forged DNS records into the resolver cache.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-11-08 02:01:55 UTC
Hickory DNS hickory-net 0.26.0-beta.1 before 0.26.2 and hickory-proto 0.24.0 through 0.26.0-alpha.1 compare DNSKEY public keys against DNSSEC trust anchors without checking the DNSKEY record name, so an RRset made up only of trusted keys is accepted without RRSIG verification. Attackers able to spoof or control name server responses can replace a secure zone's DNSKEY RRset with the root zone's keys, and use a large TTL to keep it cached.