Skip to main content
Mallory
LowVulnerability

CVE-2026-41637: DNS-over-QUIC waiting-reply exhaustion in NLnet Labs Unbound

Published Jul 22, 2026 · Updated 11 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS3.7Low · v3.1
EPSS0.37%31st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Nlnet Labs
IdentifiersCVE-2026-41637CWE-772 · Missing Release of Resource after…

NLnet Labs Unbound versions 1.22.0 through 1.25.1 inclusive improperly account for client-terminated DNS-over-QUIC (DoQ) queries. Queries terminated using QUIC STOP_SENDING, RESET_STREAM, or CONNECTION_CLOSE frames remain counted as waiting replies for in-flight resolutions. Repeatedly submitting and immediately terminating queries can inflate this count until the waiting-reply limit is reached, causing Unbound to silently drop new client queries for the affected in-flight resolutions.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An unauthenticated remote attacker can degrade DNS resolution availability by exhausting waiting-reply capacity for in-flight resolutions. Legitimate clients requesting those resolutions experience silent query drops and resolution failures or delays. The vulnerability has a low availability impact; no confidentiality or integrity impact is identified.

Mitigation

If you can’t patch tonight, do this now.

Until patched, disable DNS-over-QUIC if it is unnecessary by removing the quic-port configuration from listening interfaces, or use an Unbound build without DoQ support. Restrict network access to the DoQ listener to trusted clients. Retain the per-source wait-limit protection, but do not rely on it alone: attackers using multiple source IP addresses can bypass that protection.

Remediation

Patch, then assume compromise.

Upgrade Unbound to version 1.25.2 or later, or install a distribution package containing the fix. For Debian 13 (trixie), upgrade the affected Unbound packages to version 1.26.1-0+deb13u1 or a subsequent security-fixed version.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Nlnet LabsUnboundapplication
FAQ

Frequently asked questions

Is CVE-2026-41637 exploited in the wild?
As of Nov 7, 2026, Mallory has no reports of CVE-2026-41637 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-41637?
As of Nov 7, 2026, Mallory has found no public exploit for CVE-2026-41637.
Is there a patch for CVE-2026-41637?
Upgrade Unbound to version 1.25.2 or later, or install a distribution package containing the fix. For Debian 13 (trixie), upgrade the affected Unbound packages to version 1.26.1-0+deb13u1 or a subsequent security-fixed version.
What products are affected by CVE-2026-41637?
Nlnet Labs Unbound.
How severe is CVE-2026-41637?
CVE-2026-41637 has a CVSS v3.1 score of 3.7 (Low) and an EPSS score of 0.37% (31st percentile) as of Nov 7, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.