CVE-2026-41637

LOWPre-NVD 3.73.7
EchelonGraph scoreHIGH confidence

Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-07-22. a secondary CVSS source baseline 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
Trending — 4 sources updated this week
3.7
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 3.7Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
3.7
EG Score
3.7(high)
EG Risk
17(Track)
EG Risk 17/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity37% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
27.5%
KEV
Not listed

Published

July 22, 2026

Last Modified

July 22, 2026

Vendor Advisories for CVE-2026-41637(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 8× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:11 UTCEG score recompute
  3. 2026-07-22 22:04 UTCEG score recompute
  4. 2026-07-22 22:04 UTCGHSA enrichment
  5. 2026-07-22 15:34 UTCEG score recompute
  6. 2026-07-22 15:34 UTCGHSA enrichment
  7. 2026-07-22 13:18 UTCEG score recompute
  8. 2026-07-22 13:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-41637?
CVE-2026-41637 is a low vulnerability published on July 22, 2026. 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…
When was CVE-2026-41637 disclosed?
CVE-2026-41637 was first published in the National Vulnerability Database on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41637 actively exploited?
CVE-2026-41637 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41637?
CVE-2026-41637 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-41637?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41637, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-41637

Explore →

Is Your Infrastructure Affected by CVE-2026-41637?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.