CVE-2026-54873

QUIC STREAM Fragment Metadata DoS

Published Sep 29, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
Issue summary: QUIC process may keep memory for QUIC packet
buffer for much longer period than necessary.

Impact summary: Remote peer can exploit this vulnerability
by sending maliciously crafted packets, making the local
QUIC stack to keep the memory for packet buffers allocated.
The time for which the memory remains allocated is entirely
under the control of the potentially malicious remote peer.

CWE: CWE-770: Allocation of Resources Without Limits or Throttling

Description: To save copy operation from the packet buffer to the
stream reassemble buffer the QUIC stack leaves the stream data
on the packet buffer waiting to be copied to a buffer provided
by the local receiving application. The QUIC stack releases
a reference to the packet buffer only after the data are copied
to the application buffer. This design is more efficient for
legitimate data transfers but enables an attacker to allocate a lot
more memory than actually required by the data kept in the receiving
stream buffer.

To mitigate the vulnerability, the QUIC stack now calculates
and monitors memory overhead for every stream. The memory overhead
for a single stream frame is calculated as a difference between the
size of the whole packet that carries the stream frame and the size
of the stream frame itself. The memory overhead for a single stream
frame is added to the total (cumulative) memory overhead QUIC stack
keeps for each stream. Once the cumulative memory overhead exceeds
64kB, the QUIC stack moves the stream frame data from the packet
buffer to the stream buffer, starting with the next packet received.

FIPS impact: no
The FIPS module is not affected as the QUIC implementation is outside of
the OpenSSL FIPS module boundary.

Analysis

AI-generated

Technical impact

The vulnerability arises because the OpenSSL QUIC stack keeps packet buffers allocated for longer than necessary when reassembling stream data. A remote peer can send maliciously crafted QUIC packets and control how long these buffers remain allocated. The excessive allocation of memory, limited only by the size of the data queued for reassembly, can deplete system resources and lead to a denial of service. This weakness is a classic example of Allocation of Resources Without Limits, reflected in CWE‑770.

Affected Systems

The affected product is OpenSSL. No specific sub‑version information is listed in the CVE data, so any build of OpenSSL containing the pre‑patch QUIC implementation may be vulnerable.

Risk and Exploitability

The attack vector is remote, inferred from the description that a malicious peer can send crafted packets. The EPSS score is < 1%, and the vulnerability is not listed in the CISA KEV catalog. Exploitation requires only network connectivity to a QUIC‑enabled OpenSSL instance; no special privileges are needed. Because the attacker can control how long buffers remain allocated, the impact is primarily on availability through memory exhaustion, and the CVSS score of 7.5 indicates a high severity.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update OpenSSL to a version that includes the QUIC buffer memory limit patch referenced in the listed commits
  • Restart any services or applications that link against the updated OpenSSL library so the fix takes effect
  • If upgrading is not possible, disable QUIC support in the affected application to eliminate the attack surface

Generated by OpenCVE AI on September 30, 2026 at 23:42 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DSA Debian DSA DSA-6531-1 openssl security update
Ubuntu USN Ubuntu USN USN-8861-1 OpenSSL vulnerabilities
History
Type Values Removed Values Added
CPEs cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

threat_severity

Moderate

Type Values Removed Values Added
First Time appeared Openssl
Openssl openssl
Vendors & Products Openssl
Openssl openssl
Type Values Removed Values Added
Description Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.
Title QUIC STREAM Fragment Metadata DoS
Weaknesses CWE-770
References
Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
openssl
Published
Updated
Sep 30, 2026, 8:11 PM
Reserved
Jun 16, 2026, 10:18 AM
Status
Analyzed
Published
Sep 29, 2026, 4:17 PM
Modified
Oct 8, 2026, 1:19 AM
Severity
Moderate
Public date
Sep 29, 2026, 3:32 PM