CVE-2026-63075: 
OpenSSL vulnerability analysis and mitigation

CVE-2026-63075 is a Denial of Service vulnerability in the OpenSSL QUIC stack caused by unbounded memory growth when processing traffic from a malicious peer. When OpenSSL sends ACK-only packets in response to ack-eliciting frames (e.g., PING frames), the implementation incorrectly stores metadata for those ACK-only packets in the TX history indefinitely, even though the QUIC protocol does not require the peer to acknowledge them. Affected versions include OpenSSL 3.4.0–3.4.6, 3.5.0–3.5.7, 3.6.0–3.6.3, and 4.0.0–4.0.1. It was published on August 25, 2026, with a CVSS v3.1 base score of 7.5 (High) (GitHub Advisory, OpenSSL Advisory).

The root cause is classified as CWE-770 (Allocation of Resources Without Limits or Throttling). In the OpenSSL QUIC ACK Manager (quic_ackm.c), ACK-only packets were unconditionally stored in the TX packet history via ossl_ackm_on_tx_packet(), despite the QUIC protocol not requiring peers to acknowledge ACK-only packets. A malicious peer can exploit this by completing a QUIC handshake, then repeatedly sending PING frames to force the victim to emit ACK-only responses, while withholding acknowledgments for any ack-eliciting data — causing the TX history to grow without bound for the lifetime of the connection. The fix introduces a new function ossl_ackm_on_tx_ack_only_packet() that updates only the highest_sent packet number without retaining the full packet record, and a helper txp_pkt_is_ack_only() to correctly classify such packets before dispatch (OpenSSL Commit 7c98d79, OpenSSL Commit bf84721).

Successful exploitation results in connection-scoped memory exhaustion on the OpenSSL peer, with no impact on confidentiality or integrity. The vulnerability affects availability only, but the impact can be severe under sustained traffic or with many concurrent QUIC connections, potentially causing the affected service to crash or become unresponsive. Any application or server using OpenSSL's QUIC stack (versions 3.4.x through 4.0.x) that accepts inbound QUIC connections from untrusted peers is at risk (GitHub Advisory, OpenSSL Advisory).

No public proof-of-concept exploit code is known to exist, and there is no evidence of in-the-wild exploitation at this time (GitHub Advisory). The vulnerability is automatable (no user interaction required) and requires only that the attacker complete a standard QUIC handshake — no authentication or elevated privileges are needed. The EPSS score is approximately 0.0048 (low probability of near-term exploitation). The CVE is not listed in the CISA Known Exploited Vulnerabilities catalog.

1. Identify target: Locate a server running an affected OpenSSL version (3.4.0–3.4.6, 3.5.0–3.5.7, 3.6.0–3.6.3, or 4.0.0–4.0.1) with a QUIC-enabled service exposed to the network.
2. Complete QUIC handshake: Establish a legitimate QUIC connection with the target server to satisfy the handshake requirement.
3. Send repeated PING frames: Continuously transmit QUIC PING frames to the server. Since PING frames are ack-eliciting, the server is obligated to respond with ACK-only packets.
4. Withhold acknowledgments: Do not acknowledge any ack-eliciting data sent by the server. This prevents the server from clearing TX history entries for ACK-only packets, causing them to accumulate.
5. Sustain or scale the attack: Maintain the connection (or open many concurrent connections) to maximize memory pressure, eventually exhausting available memory and causing a Denial of Service on the target (GitHub Advisory, OpenSSL Commit 7c98d79).

• Network: Sustained inbound QUIC traffic consisting predominantly of PING frames from a single peer or a small set of peers; absence of acknowledgment frames from the remote peer for extended periods.
• Process/Memory: Steadily increasing memory consumption in the OpenSSL-based server process without a corresponding increase in legitimate application load; out-of-memory (OOM) events or process crashes on QUIC-enabled services.
• Logs: Application or system logs showing memory allocation failures or OOM-killer events associated with the QUIC server process; unusually long-lived QUIC connections with minimal data throughput but high packet counts.

Update OpenSSL to a patched release: 3.4.7, 3.5.8, 3.6.4, or 4.0.2 (OpenSSL Advisory). As interim mitigations, implement rate limiting on QUIC connections to restrict the number of ack-eliciting packets accepted from a single peer, and enforce connection timeouts or limits for peers exhibiting suspicious acknowledgment patterns. Ubuntu users should apply USN-8678-1/USN-8678-3, FreeBSD users should apply FreeBSD-SA-26:61.openssl, and SUSE/openSUSE users should apply SUSE-SU-2026:4039-1 (Ubuntu Advisory, FreeBSD Advisory, SUSE Advisory).

The vulnerability was covered by several cybersecurity news outlets as part of broader OpenSSL patch coverage, with articles noting it was one of multiple flaws addressed in the August 2026 OpenSSL release (CyberSecurityNews, GBHackers). Multiple Linux distributions (Ubuntu, SUSE, openSUSE, Debian, Alpine, FreeBSD, Slackware) issued security advisories and updated packages promptly. No notable individual researcher commentary or significant social media discussion specific to this CVE has been identified beyond standard vulnerability tracking.