In NLnet Labs Unbound 1.22.0 up to and including 1.25.1, when downstream DNS-over-QUIC (DoQ) is enabled, the first two bidirectional streams on a new QUIC connection (stream_id 0 and 4) bypass the per-stream 'quic-size' gate entirely, and large input buffers are allocated later, after only the 2-byte length prefix has been received from the initial streams. As a result, a remote client can make Unbound exceed the configured 'quic-size' limit with low-cost input. Using only one connection and two streams, each sending a declared 65535-byte length prefix and then holding the streams open, a client can already trivially make Unbound roughly allocate double that amount. This is a remote availability issue / memory-accounting bypass in the downstream DoQ implementation that leads to denial of service for new DoQ clients. This vulnerability needs Unbound to be compiled with DoQ support ('--with-libngtcp2') and the 'quic-port' to be configured for the listening interfaces.
CVE-2026-32665
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-22. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 49(Track)EG Risk 49/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 computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 21%
- KEV
- Not listed
Published
July 22, 2026
Last Modified
July 24, 2026
Advisory Details (1)
Auto-updated Jul 22, 2026Vendor Advisories for CVE-2026-32665(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2026-32665Microsoft Security Response Center (MSRC)Medium
Remote DNS-over-QUIC denial of service due to `quic-size` budget bypass
- GHSA-v3cq-93xf-4p42GitHub Security AdvisoriesHigh
In NLnet Labs Unbound 1.22.0 up to and including 1.25.1, when downstream DNS-over-QUIC (DoQ) is...
- RHSA-2026:43588Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | unbound-main-1.25.2-0.1.hum1 | 2026-07-22 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| unbound | 1.13.1-1 ... 1.25.2-1 (47 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| unbound | 1.17.1-2 ... 1.26.0-2 (25 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| unbound | 1.22.0-2 ... 1.26.0-2 (15 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| unbound | 1.22.0-2 ... 1.25.1-1 (9 versions) | 1.25.2-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 28× in last 7d / 133× 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.
Showing the most recent 100 of 280 total refreshes for this CVE.
- 2026-09-16 07:04 UTCEG score recompute
- 2026-09-16 07:04 UTCVendor advisory
- 2026-09-16 07:04 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-14 10:17 UTCVendor advisory
- 2026-09-14 10:17 UTCGHSA enrichment
- 2026-09-13 22:26 UTCEG score recompute
- 2026-09-13 22:26 UTCVendor advisory
- 2026-09-13 22:26 UTCGHSA enrichment
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-13 08:42 UTCVendor advisory
- 2026-09-13 08:42 UTCGHSA enrichment
- 2026-09-12 20:59 UTCEG score recompute
- 2026-09-12 20:59 UTCVendor advisory
- 2026-09-12 20:59 UTCGHSA enrichment
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-12 09:16 UTCVendor advisory
- 2026-09-12 09:16 UTCGHSA enrichment
- 2026-09-11 21:04 UTCEG score recompute
- 2026-09-11 21:04 UTCVendor advisory
- 2026-09-11 21:04 UTCGHSA enrichment
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-11 09:21 UTCVendor advisory
- 2026-09-11 09:21 UTCGHSA enrichment
- 2026-09-10 21:38 UTCEG score recompute
Show 75 moreShow fewer
- 2026-09-10 21:38 UTCVendor advisory
- 2026-09-10 21:38 UTCGHSA enrichment
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-09 09:18 UTCEG score recompute
- 2026-09-09 09:18 UTCVendor advisory
- 2026-09-09 09:18 UTCGHSA enrichment
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 21:42 UTCEG score recompute
- 2026-09-07 21:42 UTCVendor advisory
- 2026-09-07 21:42 UTCGHSA enrichment
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 08:43 UTCVendor advisory
- 2026-09-06 08:43 UTCGHSA enrichment
- 2026-09-05 19:35 UTCEG score recompute
- 2026-09-05 19:35 UTCVendor advisory
- 2026-09-05 19:35 UTCGHSA enrichment
- 2026-09-05 07:16 UTCEG score recompute
- 2026-09-05 07:16 UTCVendor advisory
- 2026-09-05 07:16 UTCGHSA enrichment
- 2026-09-04 13:56 UTCEG score recompute
- 2026-09-04 13:56 UTCVendor advisory
- 2026-09-04 13:56 UTCGHSA enrichment
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 23:41 UTCEG score recompute
- 2026-09-01 23:41 UTCVendor advisory
- 2026-09-01 23:41 UTCGHSA enrichment
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-31 00:27 UTCEG score recompute
- 2026-08-31 00:27 UTCVendor advisory
- 2026-08-31 00:27 UTCGHSA enrichment
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 12:44 UTCEG score recompute
- 2026-08-30 12:44 UTCVendor advisory
- 2026-08-30 12:44 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-30 00:56 UTCEG score recompute
- 2026-08-30 00:56 UTCVendor advisory
- 2026-08-30 00:56 UTCGHSA enrichment
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 22:02 UTCEG score recompute
- 2026-08-27 22:02 UTCVendor advisory
- 2026-08-27 22:02 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 10:19 UTCVendor advisory
- 2026-08-27 10:19 UTCGHSA enrichment
- 2026-08-26 19:58 UTCEG score recompute
- 2026-08-26 19:58 UTCVendor advisory
- 2026-08-26 19:58 UTCGHSA enrichment
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 05:41 UTCVendor advisory
- 2026-08-26 05:41 UTCGHSA enrichment
- 2026-08-25 17:49 UTCEG score recompute
- 2026-08-25 17:49 UTCVendor advisory
- 2026-08-25 17:49 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 05:58 UTCVendor advisory
- 2026-08-25 05:58 UTCGHSA enrichment
- 2026-08-24 18:15 UTCEG score recompute
- 2026-08-24 18:15 UTCVendor advisory
- 2026-08-24 18:15 UTCGHSA enrichment
- 2026-08-24 14:17 UTCEPSS rescore
- 2026-08-24 06:14 UTCVendor advisory
- 2026-08-24 06:14 UTCGHSA enrichment
- 2026-08-23 18:26 UTCVendor advisory
- 2026-08-23 18:26 UTCGHSA enrichment
- 2026-08-23 06:43 UTCEG score recompute
- 2026-08-23 06:43 UTCVendor advisory
- 2026-08-23 06:43 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 19:01 UTCVendor advisory
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-0554EG 10.0EPSS p99HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
- CVE-2001-0011EG 10.0EPSS p94HIGH
- CVE-2001-0013EG 10.0EPSS p96HIGH
Same CWE
10 shownCWE-1284
- CVE-2022-20699EG 10.0 KEVEPSS p99CRITICAL
- CVE-2021-21960EG 10.0CRITICAL
- CVE-2021-21951EG 10.0CRITICAL
- CVE-2021-21950EG 10.0CRITICAL
- CVE-2022-25727EG 9.8CRITICAL
- CVE-2022-36938EG 9.8CRITICAL
- CVE-2022-20385EG 9.8CRITICAL
- CVE-2022-37134EG 9.8EPSS p97CRITICAL
- CVE-2021-43267EG 9.8EPSS p99CRITICAL
- CVE-2021-31556EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-32665?
When was CVE-2026-32665 disclosed?
Is CVE-2026-32665 actively exploited?
What is the CVSS score of CVE-2026-32665?
How do I remediate CVE-2026-32665?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32665
Is Your Infrastructure Affected by CVE-2026-32665?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.