CVE-2026-54873
Received Received - Intake

QUIC Stack Memory Allocation Vulnerability in OpenSSL

Vulnerability report for CVE-2026-54873, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-29

Last updated on: 2026-09-29

Assigner: OpenSSL Software Foundation

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-29
Last Modified
2026-09-29
Generated
2026-09-29
AI Q&A
2026-09-29
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 5 associated CPEs
Vendor Product Version / Range
openssl quic *
openssl openssl 4.0.3
openssl openssl 3.6.5
openssl openssl 3.5.9
openssl openssl 3.4.8

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-770 The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves a QUIC process retaining memory for packet buffers longer than necessary. An attacker can send crafted packets to force the local QUIC stack to keep excessive memory allocated. The memory retention duration is controlled by the remote peer, potentially leading to resource exhaustion.

Detection Guidance

This vulnerability is specific to OpenSSL's QUIC implementation and requires monitoring memory usage of QUIC streams. Check if your OpenSSL version is vulnerable by running: openssl version. If using affected versions (4.0, 3.6, 3.5, 3.4), upgrade immediately. Monitor QUIC stream memory usage with tools like netstat, ss, or lsof to detect unusually high memory consumption per stream.

Impact Analysis

An attacker could exploit this to consume excessive memory on your system by sending specially crafted packets. This may lead to degraded performance, crashes, or denial of service due to resource exhaustion.

Compliance Impact

This vulnerability primarily involves memory exhaustion through crafted QUIC packets, which could lead to denial-of-service conditions. While not directly impacting data privacy or confidentiality, such resource exhaustion attacks may indirectly affect compliance by disrupting services handling sensitive data under GDPR or HIPAA. However, the provided context does not specify direct compliance impacts.

Mitigation Strategies

Update to the latest version of OpenSSL that includes the fix for this QUIC memory allocation issue. The mitigation involves monitoring memory overhead per stream and moving data to stream buffers once cumulative overhead exceeds 64kB.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-54873. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart