CVE-2026-14456: 
OpenSSL vulnerability analysis and mitigation

CVE-2026-14456 is a Denial of Service vulnerability in the OpenSSL QUIC server implementation caused by unbounded memory growth in the incoming channel queue. When a QUIC server (Listener SSL object) processes valid QUIC Initial packets for unknown destination connection IDs, it allocates and queues new channel objects without enforcing any limit. The vulnerability affects OpenSSL 3.5.0–3.5.7, 3.6.0–3.6.3, and 4.0.0–4.0.1; versions prior to 3.5 (including 3.4, 3.0, 1.1.1, and 1.0.2) are not affected. It was reported on June 25, 2026 by Filipe Casal (Trail of Bits) in collaboration with OpenAI, and publicly disclosed on August 13, 2026. The CVSS v3.1 base score is 7.5 (High) (GitHub Advisory, oss-security).

The root cause is CWE-770 (Allocation of Resources Without Limits or Throttling). The port_default_packet_handler function in ssl/quic/quic_port.c uses the Connection-ID from an inbound QUIC packet header to look up an existing connection. If no match is found and the packet type is INITIAL, the function unconditionally allocates a new QUIC_CHANNEL object and appends it to the pending incoming channel list, where it awaits acceptance via SSL_accept(). Because no upper bound was enforced on this list, a remote attacker can flood the server with crafted QUIC Initial packets bearing novel connection IDs, causing the pending queue — and thus server memory — to grow without limit. The fix adds a max_pending_channels field (defaulting to 256) to the QUIC_PORT structure and silently discards new Initial packets when the queue is full; the limit is configurable via SSL_set_value_uint() with SSL_VALUE_QUIC_MAX_PENDING_CONNS (GitHub Advisory, OpenSSL commit 08e7756).

Successful exploitation causes unbounded memory consumption on the QUIC server, potentially exhausting available system memory and rendering the QUIC listener unavailable — a pure availability impact with no confidentiality or integrity consequences. The attack targets any application using OpenSSL's QUIC server API (introduced in OpenSSL 3.5) that cannot call SSL_accept() fast enough to drain the pending connection queue. The FIPS module is not affected, as the QUIC implementation resides outside the OpenSSL FIPS boundary (oss-security, GitHub Advisory).

No public proof-of-concept exploit code has been reported, and there is no evidence of in-the-wild exploitation at this time (GitHub Advisory). The attack is fully unauthenticated, requires no user interaction, and is automatable over the network, making it straightforward to execute against any exposed QUIC server running a vulnerable OpenSSL version. The EPSS score is approximately 0.465% (39th percentile), indicating a relatively low near-term exploitation probability. The vulnerability is not currently listed in the CISA Known Exploited Vulnerabilities catalog (GitHub Advisory).

1. Reconnaissance: Identify internet-facing servers running applications that use OpenSSL 3.5.x, 3.6.x, or 4.0.x QUIC server APIs (e.g., HTTP/3 servers). Tools such as Shodan or Censys can be used to locate hosts advertising QUIC/HTTP3 on UDP port 443.
2. Craft QUIC Initial packets: Generate a high volume of valid QUIC Initial packets, each containing a unique, previously unseen Destination Connection ID. Standard QUIC libraries or custom packet-crafting tools (e.g., quic-go, aioquic, or raw UDP sockets) can be used to produce these packets.
3. Flood the target: Transmit the crafted packets to the target server's QUIC listener at a rate exceeding the application's ability to call SSL_accept() and drain the pending connection queue.
4. Exhaust server memory: Each unaccepted Initial packet causes OpenSSL to allocate a new QUIC_CHANNEL object and insert it into the unbounded pending queue. Sustained flooding causes memory to grow without limit, eventually exhausting system resources and making the QUIC listener unresponsive (oss-security, OpenSSL commit 08e7756).

• Network: Sudden spike in inbound UDP traffic to the QUIC listener port (typically UDP/443) from one or more source IPs; high volume of QUIC Initial packets with diverse, non-repeating Destination Connection IDs.
• Process/System: Rapid and sustained growth in memory consumption of the QUIC server process; OOM (out-of-memory) killer events or process crashes on the server host.
• Logs: Application logs showing a large backlog of unaccepted QUIC connections; system logs (dmesg, /var/log/syslog) recording memory allocation failures or OOM events tied to the server process.
• Metrics: Monitoring dashboards showing the pending QUIC connection queue depth approaching or exceeding expected thresholds; elevated UDP packet drop rates after memory exhaustion begins.

Upgrade OpenSSL to a patched release: 3.5.8, 3.6.4, or 4.0.2 (or later), which introduce a default limit of 256 pending connections. Because OpenSSL rated this issue as Low severity, new releases were not issued immediately; the fix is available in git commits f2f1465 (4.0 branch), 4084152 (3.6 branch), and 08e7756 (3.5 branch) and will be included in the next scheduled releases (oss-security). As a workaround prior to patching, deploy network-level rate limiting on inbound QUIC (UDP) traffic to restrict the packet rate from individual sources, and ensure the application calls SSL_accept() as frequently as possible to drain the pending queue. Applications that have applied the patch can also tune the limit via SSL_set_value_uint() with SSL_VALUE_QUIC_MAX_PENDING_CONNS (OpenSSL commit 08e7756).

The vulnerability was disclosed via the OpenSSL Security Advisory on August 13, 2026, authored by Tomas Mraz, and simultaneously posted to the oss-security mailing list (oss-security). OpenSSL classified the severity as Low internally, though the CVSS score of 7.5 maps to High, reflecting the limited deployment scope of the QUIC server feature. Coverage appeared in The Hacker News in the context of broader HTTP/3 denial-of-service research (The Hacker News). No significant social media controversy or researcher debate has been observed beyond standard vulnerability tracking.