[From nobody Fri Nov 13 12:05:08 2026
Received: (at submit) by bugs.debian.org; 10 Nov 2026 11:09:20 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-3.9 required=4.0 tests=BAYES_00,FOURLA,
 FVGT_m_MULTI_ODD,SPF_HELO_NONE,SPF_PASS autolearn=no
 autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 78; hammy, 150; neutral, 164; spammy,
 0. spammytokens:
 hammytokens:0.000-+--UD:security-tracker.debian.org, 
 0.000-+--security-tracker.debian.org,
 0.000-+--securitytrackerdebianorg, 0.000-+--H*r:jmm,
 0.000-+--sk:team@se
Return-path: &lt;jmm@inutil.org&gt;
Received: from inutil.org ([51.38.114.215]:53256 helo=vps-b7ad3695.vps.ovh.net)
 by buxtehude.debian.org with esmtp (Exim 4.96)
 (envelope-from &lt;jmm@inutil.org&gt;) id 1xQjj5-00CADd-0o
 for submit@bugs.debian.org; Tue, 10 Nov 2026 11:09:20 +0000
Received: from soju.westfalen.local
 (static-219-192-78-212.thenetworkfactory.nl [212.78.192.219])
 by vps-b7ad3695.vps.ovh.net (Postfix) with ESMTPSA id 37F711F7
 for &lt;submit@bugs.debian.org&gt;; Tue, 10 Nov 2026 11:09:18 +0000 (UTC)
Received: from jmm by soju.westfalen.local with local (Exim 4.100.1)
 (envelope-from &lt;jmm@soju.westfalen.local&gt;) id 1xQjj3-00000000JfJ-3rk7
 for submit@bugs.debian.org; Tue, 10 Nov 2026 12:09:17 +0100
Date: Tue, 10 Nov 2026 12:09:17 +0100
To: submit@bugs.debian.org
Subject: rust-hickory-recursor: CVE-2026-123598 CVE-2026-123602
 CVE-2026-123603 CVE-2026-123583 CVE-2026-123586 CVE-2026-123588
Message-ID: &lt;avL7XaXYwofLXnAy@pisco.westfalen.local&gt;
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
From: =?UTF-8?Q?Moritz_M=C3=BChlenhoff?= &lt;jmm@inutil.org&gt;
Delivered-To: submit@bugs.debian.org

Source: rust-hickory-recursor
X-Debbugs-CC: team@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for rust-hickory-recursor.

CVE-2026-123598[0]:
| 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.

https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-29q9-p769-j8gq

CVE-2026-123602[1]:
| The Hickory DNS recursor in all versions of hickory-recursor and in
| hickory-resolver 0.26.0-beta.1 before 0.26.2 (recursor feature) is
| vulnerable to ghost domain names attacks because it reuses child-
| side apex NS RRsets cached from zone NS queries for iterative
| resolution. By repeatedly querying a zone's NS records, an attacker
| keeps the stale RRset cached indefinitely, letting name servers
| whose delegation the parent revoked keep answering for the zone.

https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-2hxp-x833-73f7

CVE-2026-123603[2]:
| hickory-proto and hickory-resolver 0.26.0 before 0.26.2, hickory-
| server 0.25.0-alpha.1 before 0.26.2, and hickory-recursor
| 0.25.0-alpha.3 through 0.26.0-alpha.1 fail to canonicalize
| IPv4-mapped IPv6 addresses when checking deny_answers, deny_server,
| or AccessControlSet rules. Attackers can use IPv4-mapped addresses
| to evade answer filtering, trigger queries to denied nameservers, or
| reach hickory-server library deployments on dual-stack IPv6 sockets
| from denied clients.

https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-4jwp-xjwm-333g

CVE-2026-123583[3]:
| The recursive resolver in Hickory DNS hickory-recursor 0.25.0
| through 0.25.2 and hickory-resolver 0.26.0 before 0.26.2 does not
| apply out-of-bailiwick filtering to negative responses. Attackers
| able to supply crafted negative responses can include out-of-
| bailiwick records to facilitate cache poisoning and more easily
| exploit other DNSSEC verification flaws.

https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-vcjp-57rr-mpfw

CVE-2026-123586[4]:
| Hickory DNS 0.25.0-alpha.3 through 0.25.2 contains a query
| amplification vulnerability in its recursive resolver, which
| mishandles cyclic sibling name server referrals that lack glue
| records. Attackers controlling two zones whose name servers
| reference each other without glue records can make the recursor
| loop, sending many upstream queries, amplified further by zero-TTL
| NS records.

https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-cx5j-p54p-q756

CVE-2026-123588[5]:
| The recursive resolver in Hickory DNS (all versions of the hickory-
| recursor crate, and hickory-resolver 0.26.0 before 0.26.2) caches an
| empty connection pool when it follows a referral with no glue
| records and all queries for the name servers' IP addresses fail. An
| attacker able to spoof DNS responses can make these lookups fail,
| causing all subsequent queries for the affected zone to fail until
| the cache entry expires or is evicted.

https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-9px7-7m25-f6q2


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities &amp; Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2026-123598
    https://www.cve.org/CVERecord?id=CVE-2026-123598
[1] https://security-tracker.debian.org/tracker/CVE-2026-123602
    https://www.cve.org/CVERecord?id=CVE-2026-123602
[2] https://security-tracker.debian.org/tracker/CVE-2026-123603
    https://www.cve.org/CVERecord?id=CVE-2026-123603
[3] https://security-tracker.debian.org/tracker/CVE-2026-123583
    https://www.cve.org/CVERecord?id=CVE-2026-123583
[4] https://security-tracker.debian.org/tracker/CVE-2026-123586
    https://www.cve.org/CVERecord?id=CVE-2026-123586
[5] https://security-tracker.debian.org/tracker/CVE-2026-123588
    https://www.cve.org/CVERecord?id=CVE-2026-123588

Please adjust the affected versions in the BTS as needed.
]