CVE-2026-75804
Description
A flaw was found in OpenSSL. A remote attacker can cause a Denial of Service (DoS) due to missing connection-level flow control enforcement in the QUIC protocol implementation. By opening multiple streams that respect individual stream limits while preventing data consumption, the attacker can force the system to buffer far more data than permitted by the connection limit. This excessive memory allocation can exhaust available system resources and degrade or terminate the service.
Statement
A denial of service vulnerability of moderate severity was found in the OpenSSL QUIC implementation. The QUIC stack enforces the per-stream flow control limit but does not enforce the connection-level flow control limit. A remote, unauthenticated peer can exploit this by opening multiple streams that each stay within the per-stream limit while sending no zero-offset byte (which prevents the stack from consuming the data), forcing the local QUIC stack to buffer far more data than the connection limit permits. With default settings (a maximum of 200 streams and a 512 KiB per-stream window), a malicious peer can drive the stack to allocate roughly 100 MB of heap per connection instead of the default 768 KiB connection window, which can exhaust memory and degrade or terminate the affected service. There is no impact on confidentiality or integrity. Red Hat rates this issue as Moderate severity (CVSS 3.1 score 5.3, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L), whereas upstream OpenSSL classified it as Low severity.
Only OpenSSL versions that contain the QUIC stack are affected. Red Hat Enterprise Linux streams shipping OpenSSL 1.x (including the openssl 1.0.x/1.1.1, compat-openssl10, compat-openssl11, and mingw-openssl 1.x components on RHEL 6, 7, and 8 streams) are not affected because the vulnerable QUIC code is not present in those versions. Affected Red Hat products that ship an OpenSSL version with the QUIC stack are being addressed through their respective update streams; for a number of these products the fix is deferred to a future scheduled update given the denial-of-service-only nature of this flaw. The residual risk of deferral is limited to remote memory-exhaustion denial of service against applications that use the OpenSSL QUIC API. The OpenSSL FIPS module is not affected because the QUIC implementation is outside the FIPS module boundary.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.3 | N/A | 5.3 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | None | N/A | None |
| Availability Impact | Low | N/A | Low |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)
When allocating resources without limits, an attacker could prevent other systems, applications, or processes from accessing the same type of resource. It can be easy for an attacker to consume many resources by rapidly making many requests or causing larger resources to be used than is needed.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.