Degradation of resolution service from improperly accounted client-terminated DNS-over-QUIC queries
CVE-2026-41637 is fixed in unbound on 1 platform, first by DEBIAN-CVE-2026-41637, released July 28, 2026. It is not reported as exploited. Patch Radar priority: Routine.
In NLnet Labs Unbound 1.22.0 up to and including 1.25.1, client terminated DNS-over-QUIC (DoQ) queries are not accounted properly by Unbound resulting in low-cost inflation of the waiting number of replies for already in-flight resolution queries. This results in degradation of resolution service for new clients for already in-flight queries. A malicious actor can exploit the vulnerability by issuing DoQ queries for query names that need resolution and proceeding on immediately terminating the query by one of STOP_SENDING/RESET_STREAM/CONNECTION_CLOSE QUIC frames. Those terminated DoQ queries are not properly counted for and keep inflating the number of waiting replies for in-flight queries. When the maximum is reached, it results in silent query drops for new clients needing resolution for already in-flight queries. This vulnerability needs Unbound to be compiled with DoQ support ('--with-libngtcp2') and the 'quic-port' to be configured for the listening interfaces. Additionally, a malicious actor needs access to multiple source IPs to bypass the by-default configured 'wait-limit' option.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| unbound · Debian 13.5 (trixie) | 1.26.1-0+deb13u1 | DEBIAN-CVE-2026-41637 | Jul 28, 2026 |
| unbound · Debian 14 | 1.25.2-1 | DEBIAN-CVE-2026-41637 | Jul 28, 2026 |
| unbound · opensuse-leap 16.0 | 1.25.2-160000.1.1 | OPENSUSE-SU-2026:21550-1 | Aug 10, 2026 |
| unbound · sles 16.0 | 1.25.2-160000.1.1 | SUSE-SU-2026:23226-1 | Aug 10, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.