CVE-2026-12708: Cloudflare tokio-quiche · Memory Leak
Affects Cloudflare tokio-quicheSource CVE Database V5
Not known to be exploited · CVSS 8.7 High · patch available : patch Cloudflare tokio-quiche soon.
Data as of 10 Nov 2026, 13:35 UTC
Thin evidence
One scorer or none| CNA (cloudflare) | CVSS 4.0 | 8.7 |
|---|
- Patch
- Available
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Cloudflaretokio-quiche | Affected
| Fixed in– |
GitHubtokio-quichepkg:github/tokio-quicheOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Disable DATAGRAM support by setting QuicSettings::enable_dgram to false in tokio-quiche. Alternatively, upgrade to version 0.23.0 or later, which includes a fix that bounds flow state creation to valid DATAGRAM-capable streams and manages early DATAGRAMs with bounded buffers or discards.
Description
Cloudflare's tokio-quiche library contains a resource consumption vulnerability in its HTTP/3 DATAGRAM handling. The issue arises because the library creates and retains new per-flow state for every previously unseen flow identifier received in a DATAGRAM frame, which can grow without bound. This can lead to exhaustion of process memory and denial of service. The vulnerability affects both client and server configurations when DATAGRAM support is enabled. Disabling DATAGRAM support or upgrading to version 0.23.0 or later mitigates the issue.