CVE-2026-14456

Issue summary: When an OpenSSL QUIC server (Listener SSL object) processes valid QUIC Initial packets for unknown destination connection IDs, it can allocate and queue new incoming channels without enforcing any limit. Impact summary: A remote peer that can make many Initial packets reach the server listener faster than the application accepts connections, can cause the memory allocated to store the per-channel state to grow without any limits, potentially making the QUIC listener unavailable and causing Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The function that handles inbound QUIC packets uses Connection-Id from the packet header to find an existing connection (QUIC channel). If no existing connection is found and the packet type is INITIAL, the function treats the packet as a new connection. It allocates a new channel object and inserts it into a queue where it waits to be accepted by the local application with SSL_accept(3ossl). The memory occupied by these initial channel objects may grow without bounds if the application is not able to call SSL_accept() frequently enough to serve these inbound connection requests. The issue is present since OpenSSL 3.5 when the QUIC server implementation was added. The fix introduces a limit for pending connections. The default limit is set to 256 pending connections (waiting to be accepted by the local application). Applications may change the default by calling SSL_set_value_uint(3ossl). FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.

• CWE-770

• https://github.com/openssl/openssl/commit/08e7756c3900bcfd77a720e7b74e27d6e4ed01a9
• https://github.com/openssl/openssl/commit/4084152e040329ca0194c4c1750b9b46d00a5b6b
• https://github.com/openssl/openssl/commit/f2f1465f2d2e5c61dfeac4d20fd093797d821139
• https://openssl-library.org/news/secadv/20260813.txt
• https://www.openwall.com/lists/oss-security/2026/08/13/4

Published

Aug 13, 2026

Last Modified

Aug 28, 2026

Status

Awaiting Analysis

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-14448An high privileged remote attacker can exploit an authentica…8.6
• CVE-2026-14449u5CMS through v12.8.8 is vulnerable to reflected XSS via the…6.4
• CVE-2026-1445A vulnerability was found in iJason-Liu Books_Manager up to …4.7
• CVE-2026-14450A flaw was found in the MaaS API. This vulnerability allows …9.9
• CVE-2026-14453This vulnerability is a critical Server-Side Template Inject…9.6
• CVE-2026-14454Imager versions before 1.033 for Perl treat unsigned EXIF IF…9.8
• CVE-2026-14457Issue summary: In a server or client configuration with RFC7…7.5
• CVE-2026-14459Improper neutralization of argument delimiters in a command …8.8
• CVE-2026-1446There is a Cross‑Site Scripting (XSS) issue in Esri ArcGIS P…5
• CVE-2026-14460Missing Authorization vulnerability in TUBITAK BILGEM Softwa…8.8
• CVE-2026-14461mtr is vulnerable to Out-of-bound read vulnerability in ipin…5.1
• CVE-2026-14465Insufficient session expiration vulnerability in Bilin Softw…6.5