Vulnerability · Published Sep 29, 2026 · Assigned by openssl

CVE-2026-75804QUIC Connection-Level Flow Control is Not Enforced for Streams

Medium 5.3

In plain English

A medium-severity resource allocation without limits in OpenSSL from OpenSSL. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.5% (higher than 45% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)5.3Medium
Exploit odds (30 days)0.5%top 55.0% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

Issue summary: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits. Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The local QUIC stack advertises two flow control limits to its remote peer: stream flow control limit and connection flow control limit. The remote peer must follow both limits when transmitting stream data. Whenever the local QUIC stack receives a stream frame, it validates that the size of the received stream frame stays within flow control limits. If either limit is exceeded (stream level or connection level), then the QUIC stack must close the connection with a flow control error. The vulnerable OpenSSL QUIC stack enforces the stream-level but not the connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data). By meeting the conditions above, the remote peer may make the local stack allocate 2 x MAX_STREAMS x (stream flow control limit) bytes of memory. MAX_STREAMS defaults to 100, and the limit applies to both bidirectional and unidirectional streams, making it 200 in total. The default flow control window for a stream is 512kB. The remote peer may force the vulnerable QUIC stack to allocate 100MB of heap per connection. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Alpine:v3.21openssl3.3.7-r2ALPINE-CVE-2026-75804
Debian:13openssl3.5.7-1~deb13u3DEBIAN-CVE-2026-75804
Debian:14openssl3.6.5-1DEBIAN-CVE-2026-75804
Ubuntu:26.04:LTSedk2no fix listedUBUNTU-CVE-2026-75804
Ubuntu:26.10edk2no fix listedUBUNTU-CVE-2026-75804
Ubuntu:26.04:LTSedk2-hweno fix listedUBUNTU-CVE-2026-75804
Ubuntu:26.10edk2-hweno fix listedUBUNTU-CVE-2026-75804
Ubuntu:22.04:LTSopenssl3.0.2-0ubuntu1.30USN-8847-1
Ubuntu:24.04:LTSopenssl3.0.13-0ubuntu3.16USN-8847-1
Ubuntu:26.04:LTSopenssl3.5.5-1ubuntu3.6USN-8847-1
Ubuntu:26.04:LTSopenssl3.5.5-1ubuntu3.6UBUNTU-CVE-2026-75804

Affected products (as reported)

VendorProductVersions
OpenSSL OpenSSL 4.0.0 – before 4.0.33.6.0 – before 3.6.53.5.0 – before 3.5.93.4.0 – before 3.4.8

Weakness: CWE-770 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

References