Unbounded flow map growth in tokio-quiche HTTP/3 DATAGRAM handling
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- No fix listed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-401.
Summary
Cloudflare tokio-quiche from 0.0.1 through 0.20.1 keeps new per-flow state for every previously unseen flow identifier received in HTTP/3 DATAGRAM frames, with no limit (CWE-401). A remote peer that has negotiated DATAGRAM support can send DATAGRAMs with many distinct identifiers, so the per-connection flow map grows until process memory is exhausted and the service stops. Both client and server configurations are affected.
Written with Claude Haiku 5.5 from the sources below · 2026-11-10
Description from the CNA
Summary Cloudflare tokio-quiche was found to contain an uncontrolled resource consumption vulnerability in its HTTP/3 DATAGRAM handling. For every previously unseen flow identifier (quarter stream ID) received in a DATAGRAM frame, tokio-quiche creates and retains new, per-flow state. A remote peer can send DATAGRAMs with many distinct identifiers, causing the per-connection flow map and associated channel state to grow without bound. Impact Exploitation can exhaust process memory and cause a denial of service. The vulnerable code is used in both client and server configurations, so either role can be affected by a malicious peer. QUIC DATAGRAM support in tokio-quiche is enabled by default through QuicSettings::enable_dgram; applications can disable it by setting this field to false. The vulnerable HTTP/3 path is reachable only when DATAGRAM support is negotiated with the peer. Core quiche and HTTP/3 deployments without DATAGRAM support are not affected. Mitigation Disable DATAGRAMs in tokio-quiche’s QuicSettings::enable_dgram. Remediation Upgrade to tokio-quiche version 0.23.0 or later. The fixed code creates flow state only for valid DATAGRAM-capable request streams, which are bounded by QUIC’s stream limits. To tolerate packet reordering, servers retain early DATAGRAMs in a bounded, expiring buffer, while clients discard DATAGRAMs for unknown flows.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Cloudflare | tokio-quiche | 0.0.1 – 0.20.1 | — | No fix listed | CNA |
- tokio-quiche VendorCloudflare Affected 0.0.1 – 0.20.1 Fixed in — No fix listed CNA
Remediation
Upgrade tokio-quiche to version 0.23.0 or later. Until the upgrade is applied, disable DATAGRAMs by setting QuicSettings::enable_dgram to false.
Written with Claude Haiku 5.5 from the sources below · 2026-11-10
Timeline
- 2026-11-10 Threatist record created from CVE-2026-12708
- 2026-11-10 1 new reference · CNA
- 2026-11-12 Priority changed: MEDIUM → LOW
- 2026-11-13 CISA SSVC decision points changed
References
More Cloudflare vulnerabilities
- TI-2026-12208 Cloudflare Universal SSL automatically managed CAA RRset supersedes customer-configured CAA records CVSS 4.0HIGH 7.6
- TI-2025-36979 Cloudflare vite plugin exposes secrets over the built-in dev server CVSS 4.0LOW 2.9
- TI-2014-08329 Out-of-bounds write in github.com/cloudflare/golz4 CVSS 3.1CRITICAL 9.8
- TI-2021-02817 Arbitrary filepath traversal via URI injection CVSS 3.1CRITICAL 9.8
- TI-2026-02435 HTTP Request Smuggling via HTTP/1.0 and Transfer-Encoding Misparsing CVSS 4.0CRITICAL 9.3
- TI-2023-02843 Out of Bounds Slice index in cfnts leads to remote panic CVSS 3.1HIGH 8.6
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences