OpenSSL · OpenSSL · published 2026-08-25

CVE-2026-63075QUIC ACK-only Packet Retention Can Cause Memory Exhaustion

Routine No exploitation evidence; EPSS 0.6%.

CVE-2026-63075 is not known to be exploited in the wild. EPSS estimates a 0.6% chance of exploitation in the next 30 days, higher than 48% of all CVEs. This OpenSSL vulnerability: CVSS 7.5 (v3.1), attacks can be automated. Fixed upstream in OpenSSL 4.0.2, 3.6.4, 3.5.8, 3.4.7 (+3 more). Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in OpenSSL 4.0.2, 3.6.4, 3.5.8, 3.4.7, 3.0.22, 1.1.1zi, 1.0.2zr.

Patch events

  1. This monthSecurity release

    Crypto libraryOpenSSL

    OpenSSL security fixes: 9 CVEs

    Upgrade to 4.0.23.6.43.5.83.4.73.0.221.1.1zi1.0.2zr

    Why: CVE-2026-63073: EPSS 1.1% with high severity (CVSS 9.8).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.6% (49th pct)FIRST EPSS v2026.06.15
CVSS base score7.5 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →