Description
Issue summary: When OpenSSL processes QUIC traffic from a peer that repeatedly
sends ack-eliciting packets while not acknowledging ACK-only responses, the
QUIC stack can retain ACK-only packet metadata for the lifetime of the
connection.

Impact summary: A remote peer that can complete a QUIC handshake can
cause connection-scoped memory growth which may lead to Denial of Service
through memory exhaustion, especially with sustained traffic or many concurrent
QUIC connections.

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

Description: When the OpenSSL QUIC stack sends an ACK-only packet,
there is no requirement by the QUIC protocol that the peer will acknowledge
that ACK-only packet (i.e. it is itself not ack-eliciting). However, the OpenSSL
implementation stores the metadata about the ACK frames regardless.
In and of itself that's ok, but if a malicious peer establishes a connection, and
then drives the connection such that ACK-only packets are forced from the
OpenSSL implementation peer (i.e., by sending numerous PING frames),
and then withholding any subsequent acks for ack-eliciting data, like
legitimate data, said malicious peer can force inappropriate memory growth
on the OpenSSL peer, potentially leading to a Denial of Service.

The fix is to ensure that we account for the transmission of the ACK-only
packet in the packet histories high and low watermark without actually storing
the ACK-only packet metadata itself.

FIPS impact: no
The OpenSSL FIPS module is not affected as the QUIC code is
outside the FIPS module boundary.
Published: 2026-08-25
Score: 7.5 High
EPSS: < 1% Very Low
KEV: No
Impact: Denial of Service via memory exhaustion
Action: Patch Now
AI Analysis

Impact

A malfunction in OpenSSL’s QUIC stack causes the implementation to retain metadata for every ACK‑only packet without releasing it. When a malicious peer completes a QUIC handshake and repeatedly triggers ACK‑only packets—such as by sending many PING frames—and withholds ACKs for other traffic, the OpenSSL side can accumulate excessive memory usage. This unchecked growth may eventually exhaust RAM, leading to a denial of service. The weakness is a classic resource allocation flaw (CWE‑770).

Affected Systems

The flaw resides in OpenSSL’s QUIC component and therefore applies to any OpenSSL installation that supports QUIC. The vendor product affected is OpenSSL, with no publicly stated version range in the advisory. Users should consider the possibility that recent releases may also be impacted until a patch is applied.

Risk and Exploitability

A remote attacker who can establish a QUIC connection can exploit the bug. Because the defect is not limited by authentication or privileged access and the packet retention occurs for the entire lifetime of the connection, the attack can be launched from any external endpoint that the server accepts QUIC traffic on. The CVSS score is 7.5, the EPSS score is not available, and the vulnerability is not listed in CISA’s KEV catalog. Nonetheless, the potential for sustained traffic or many concurrent connections makes this a high‑risk denial of service scenario that attackers could use to cripple affected services.

Generated by OpenCVE AI on August 25, 2026 at 16:45 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the most recent OpenSSL release that incorporates the QUIC ACK‑only packet retention fix
  • If updating OpenSSL immediately is not possible, disable QUIC traffic on affected services until the patch can be deployed
  • Add monitoring or rate‑limit controls for QUIC connections to prevent runaway memory growth during a sustained attack

Generated by OpenCVE AI on August 25, 2026 at 16:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DSA Debian DSA DSA-6465-1 openssl security update
Ubuntu USN Ubuntu USN USN-8678-1 OpenSSL vulnerabilities
History

Fri, 11 Sep 2026 23:45:00 +0000

Type Values Removed Values Added
CPEs cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*

Wed, 26 Aug 2026 00:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

threat_severity

Low


Tue, 25 Aug 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics 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'}

ssvc

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


Tue, 25 Aug 2026 15:00:00 +0000

Type Values Removed Values Added
First Time appeared Openssl
Openssl openssl
Vendors & Products Openssl
Openssl openssl

Tue, 25 Aug 2026 13:15:00 +0000

Type Values Removed Values Added
Description Issue summary: When OpenSSL processes QUIC traffic from a peer that repeatedly sends ack-eliciting packets while not acknowledging ACK-only responses, the QUIC stack can retain ACK-only packet metadata for the lifetime of the connection. Impact summary: A remote peer that can complete a QUIC handshake can cause connection-scoped memory growth which may lead to Denial of Service through memory exhaustion, especially with sustained traffic or many concurrent QUIC connections. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: When the OpenSSL QUIC stack sends an ACK-only packet, there is no requirement by the QUIC protocol that the peer will acknowledge that ACK-only packet (i.e. it is itself not ack-eliciting). However, the OpenSSL implementation stores the metadata about the ACK frames regardless. In and of itself that's ok, but if a malicious peer establishes a connection, and then drives the connection such that ACK-only packets are forced from the OpenSSL implementation peer (i.e., by sending numerous PING frames), and then withholding any subsequent acks for ack-eliciting data, like legitimate data, said malicious peer can force inappropriate memory growth on the OpenSSL peer, potentially leading to a Denial of Service. The fix is to ensure that we account for the transmission of the ACK-only packet in the packet histories high and low watermark without actually storing the ACK-only packet metadata itself. FIPS impact: no The OpenSSL FIPS module is not affected as the QUIC code is outside the FIPS module boundary.
Title QUIC ACK-only Packet Retention Can Cause Memory Exhaustion
Weaknesses CWE-770
References

cve-icon MITRE

Status: PUBLISHED

Assigner: openssl

Published:

Updated: 2026-08-25T14:36:51.928Z

Reserved: 2026-07-15T13:10:26.188Z

Link: CVE-2026-63075

cve-icon Vulnrichment

Updated: 2026-08-25T14:36:45.738Z

cve-icon NVD

Status : Analyzed

Published: 2026-08-25T13:19:26.413

Modified: 2026-09-11T21:17:05.403

Link: CVE-2026-63075

cve-icon Redhat

Severity : Low

Publid Date: 2026-08-25T16:05:51Z

Links: CVE-2026-63075 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-25T17:00:04Z

Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling