5.3

CVE-2026-75804: openssl

CVSS: 5.3v3.1MediumAnalyzed
AliasesALPINE-CVE-2026-75804UBUNTU-CVE-2026-75804DEBIAN-CVE-2026-75804
Published 29-09-2026Last modified 29-09-2026

Vulnerability summary

CVE-2026-75804 is a medium (CVSS 5.3) vulnerability in openssl. EPSS estimates a 0.35% chance of exploitation in the next 30 days, higher than 27.3% of scored vulnerabilities.

Overall risk
21/100
0100
Low · default modelHow is this calculated?
CVSS score
5.3/10
010
Medium · v3.1 (CVE.org)
EPSS score
0.35%
0%100%
Low · Change unavailable
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 6 · Related 3

Timeline

  1. 29-09-2026
    PublishedVulnerability first disclosed.
  2. 29-09-2026
    Last modifiedVulnerability information updated.

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.

CVSS metrics

6 scores · 6 sources · 1 version

EPSS trend

Probability

0.35%

Chance of exploitation in the next 30 days

Percentile

27%

Versus all other CVEs

30-day change

Change unavailable

Change unavailable

30-09-202619-10-2026
EPSS score
0.35%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Chainguard4 products
  • openssl-provider-fips-3.4.0All versions (No fix recorded)
  • openssl-provider-fips-3.4.0-dbgAll versions (No fix recorded)
  • openssl-provider-fips-3.6.0All versions (No fix recorded)
  • openssl-provider-fips-3.6.0-dbgAll versions (No fix recorded)
Ubuntu4 products
  • edk2All versions (No fix recorded)
  • edk2-hweAll versions (No fix recorded)
  • nodejsAll versions (No fix recorded)
  • openssl< 3.5.5-1ubuntu3.6
Alpine1 product
  • openssl≥ 3.4.0, < 3.3.7-r2
Debian1 product
  • openssl< 3.5.7-1~deb13u3 | < 3.6.5-1
Openssl1 product
  • openssl≥ 3.4.0, < 3.4.8 | ≥ 3.5.0, < 3.5.9 | ≥ 3.6.0, < 3.6.5 | ≥ 4.0.0, < 4.0.3

5 vendors · 11 products

References

12 links
Show all 12 references