CVE-2026-32665

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

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 computed
Severity75% × 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, 2026
No patch confirmed yet.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatunbound-main-1.25.2-0.1.hum12026-07-22redhat

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)
PackageVulnerable rangeFixed inDependents
unbound1.13.1-1 ... 1.25.2-1 (47 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
unbound1.17.1-2 ... 1.26.0-2 (25 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
unbound1.22.0-2 ... 1.26.0-2 (15 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
unbound1.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.

  1. 2026-09-16 07:04 UTCEG score recompute
  2. 2026-09-16 07:04 UTCVendor advisory
  3. 2026-09-16 07:04 UTCGHSA enrichment
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-14 10:17 UTCVendor advisory
  6. 2026-09-14 10:17 UTCGHSA enrichment
  7. 2026-09-13 22:26 UTCEG score recompute
  8. 2026-09-13 22:26 UTCVendor advisory
  9. 2026-09-13 22:26 UTCGHSA enrichment
  10. 2026-09-13 16:47 UTCEPSS rescore
  11. 2026-09-13 08:42 UTCVendor advisory
  12. 2026-09-13 08:42 UTCGHSA enrichment
  13. 2026-09-12 20:59 UTCEG score recompute
  14. 2026-09-12 20:59 UTCVendor advisory
  15. 2026-09-12 20:59 UTCGHSA enrichment
  16. 2026-09-12 15:01 UTCEPSS rescore
  17. 2026-09-12 09:16 UTCVendor advisory
  18. 2026-09-12 09:16 UTCGHSA enrichment
  19. 2026-09-11 21:04 UTCEG score recompute
  20. 2026-09-11 21:04 UTCVendor advisory
  21. 2026-09-11 21:04 UTCGHSA enrichment
  22. 2026-09-11 14:52 UTCEPSS rescore
  23. 2026-09-11 09:21 UTCVendor advisory
  24. 2026-09-11 09:21 UTCGHSA enrichment
  25. 2026-09-10 21:38 UTCEG score recompute
Show 75 more
  1. 2026-09-10 21:38 UTCVendor advisory
  2. 2026-09-10 21:38 UTCGHSA enrichment
  3. 2026-09-10 09:34 UTCEPSS rescore
  4. 2026-09-09 09:18 UTCEG score recompute
  5. 2026-09-09 09:18 UTCVendor advisory
  6. 2026-09-09 09:18 UTCGHSA enrichment
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 21:42 UTCEG score recompute
  9. 2026-09-07 21:42 UTCVendor advisory
  10. 2026-09-07 21:42 UTCGHSA enrichment
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-06 08:43 UTCVendor advisory
  15. 2026-09-06 08:43 UTCGHSA enrichment
  16. 2026-09-05 19:35 UTCEG score recompute
  17. 2026-09-05 19:35 UTCVendor advisory
  18. 2026-09-05 19:35 UTCGHSA enrichment
  19. 2026-09-05 07:16 UTCEG score recompute
  20. 2026-09-05 07:16 UTCVendor advisory
  21. 2026-09-05 07:16 UTCGHSA enrichment
  22. 2026-09-04 13:56 UTCEG score recompute
  23. 2026-09-04 13:56 UTCVendor advisory
  24. 2026-09-04 13:56 UTCGHSA enrichment
  25. 2026-09-04 05:06 UTCEPSS rescore
  26. 2026-09-02 14:11 UTCEPSS rescore
  27. 2026-09-01 23:41 UTCEG score recompute
  28. 2026-09-01 23:41 UTCVendor advisory
  29. 2026-09-01 23:41 UTCGHSA enrichment
  30. 2026-09-01 13:53 UTCEPSS rescore
  31. 2026-09-01 04:39 UTCEPSS rescore
  32. 2026-09-01 04:39 UTCEPSS rescore
  33. 2026-08-31 00:27 UTCEG score recompute
  34. 2026-08-31 00:27 UTCVendor advisory
  35. 2026-08-31 00:27 UTCGHSA enrichment
  36. 2026-08-30 19:17 UTCEPSS rescore
  37. 2026-08-30 12:44 UTCEG score recompute
  38. 2026-08-30 12:44 UTCVendor advisory
  39. 2026-08-30 12:44 UTCGHSA enrichment
  40. 2026-08-30 01:22 UTCEPSS rescore
  41. 2026-08-30 00:56 UTCEG score recompute
  42. 2026-08-30 00:56 UTCVendor advisory
  43. 2026-08-30 00:56 UTCGHSA enrichment
  44. 2026-08-28 21:41 UTCEPSS rescore
  45. 2026-08-27 22:02 UTCEG score recompute
  46. 2026-08-27 22:02 UTCVendor advisory
  47. 2026-08-27 22:02 UTCGHSA enrichment
  48. 2026-08-27 14:25 UTCEPSS rescore
  49. 2026-08-27 10:19 UTCVendor advisory
  50. 2026-08-27 10:19 UTCGHSA enrichment
  51. 2026-08-26 19:58 UTCEG score recompute
  52. 2026-08-26 19:58 UTCVendor advisory
  53. 2026-08-26 19:58 UTCGHSA enrichment
  54. 2026-08-26 14:46 UTCEPSS rescore
  55. 2026-08-26 05:41 UTCVendor advisory
  56. 2026-08-26 05:41 UTCGHSA enrichment
  57. 2026-08-25 17:49 UTCEG score recompute
  58. 2026-08-25 17:49 UTCVendor advisory
  59. 2026-08-25 17:49 UTCGHSA enrichment
  60. 2026-08-25 13:49 UTCEPSS rescore
  61. 2026-08-25 05:58 UTCVendor advisory
  62. 2026-08-25 05:58 UTCGHSA enrichment
  63. 2026-08-24 18:15 UTCEG score recompute
  64. 2026-08-24 18:15 UTCVendor advisory
  65. 2026-08-24 18:15 UTCGHSA enrichment
  66. 2026-08-24 14:17 UTCEPSS rescore
  67. 2026-08-24 06:14 UTCVendor advisory
  68. 2026-08-24 06:14 UTCGHSA enrichment
  69. 2026-08-23 18:26 UTCVendor advisory
  70. 2026-08-23 18:26 UTCGHSA enrichment
  71. 2026-08-23 06:43 UTCEG score recompute
  72. 2026-08-23 06:43 UTCVendor advisory
  73. 2026-08-23 06:43 UTCGHSA enrichment
  74. 2026-08-23 00:19 UTCEPSS rescore
  75. 2026-08-22 19:01 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-32665?
CVE-2026-32665 is a high vulnerability published on July 22, 2026. 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…
When was CVE-2026-32665 disclosed?
CVE-2026-32665 was first published in the National Vulnerability Database on July 22, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32665 actively exploited?
CVE-2026-32665 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.0% of all scored CVEs.
What is the CVSS score of CVE-2026-32665?
CVE-2026-32665 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-32665?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32665, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32665

Explore →

Is Your Infrastructure Affected by CVE-2026-32665?

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