Skip to main content

OpenSSL CVE-2026-14456

| EUVDEUVD-2026-57919 HIGH
Allocation of Resources Without Limits or Throttling (CWE-770)
2026-08-13 openssl GHSA-9x89-v382-mjh7
7.5
CVSS 3.1 · Vendor: openssl
Share

Severity by source

Vendor (openssl) PRIMARY
7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
7.5 HIGH

Network-reachable QUIC listener requires no authentication or preconditions; only the listener's availability is impacted, with no confidentiality or integrity effect.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Red Hat
7.5 HIGH
qualitative

Primary rating from Vendor (openssl).

CVSS VectorVendor: openssl

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

5
Source Code Evidence Fetched
Aug 13, 2026 - 18:25 vuln.today
Analysis Generated
Aug 13, 2026 - 18:25 vuln.today
CVSS changed
Aug 13, 2026 - 18:22 NVD
7.5 (HIGH)
CVE Published
Aug 13, 2026 - 13:55 cve.org
HIGH 7.5
CVE Published
Aug 13, 2026 - 13:55 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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.

AnalysisAI

QUIC server listener in OpenSSL 3.5.x through 4.0.x allows remote unauthenticated denial of service through unbounded memory growth when processing QUIC Initial packets. Remote peers can flood the listener with Initial packets carrying novel Destination Connection IDs faster than the application drains the queue via SSL_accept(), causing per-channel state objects to accumulate without limit and exhausting process memory. No public exploit code or CISA KEV listing has been identified; vendor-confirmed patches are available in OpenSSL 3.5.8, 3.6.4, and 4.0.2.

Technical ContextAI

The vulnerability resides in OpenSSL's QUIC server-side packet dispatch code (quic_port.c), a component first introduced in OpenSSL 3.5 (CPE: cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*). When a QUIC Initial packet arrives with a Destination Connection ID not matching any existing session, the handler allocates a new QUIC channel object and appends it to an incoming_channel_list that feeds SSL_accept(). CWE-770 (Allocation of Resources Without Limits or Throttling) is the precise root cause: the list had no enforced maximum length. Commit f2f1465f introduces the SSL_VALUE_QUIC_MAX_PENDING_CONNS constant (value 16 in ssl.h.in), with DEFAULT_MAX_PENDING_CONNS set to 256 in quic_port.c. The port_default_packet_handler now checks ossl_list_incoming_ch_num() against max_pending_channels and silently discards INITIAL packets when the queue is full. Setting the limit to zero re-enables unbounded growth, which operators should avoid. The FIPS module is unaffected because the QUIC implementation sits outside the FIPS boundary.

RemediationAI

Upgrade to OpenSSL 3.5.8, 3.6.4, or 4.0.2 as appropriate for your release branch, per the vendor advisory at https://openssl-library.org/news/secadv/20260813.txt. Three upstream commits carry the fix: f2f1465f2d2e5c61dfeac4d20fd093797d821139, 4084152e040329ca0194c4c1750b9b46d00a5b6b, and 08e7756c3900bcfd77a720e7b74e27d6e4ed01a9. After upgrading, the default pending-connection limit of 256 applies automatically; operators expecting burst connection rates may tune this upward via SSL_set_value_uint() with SSL_VALUE_QUIC_MAX_PENDING_CONNS, but setting it to zero disables the cap entirely and re-exposes the vulnerability. If immediate patching is not feasible, restrict inbound QUIC traffic (UDP on the listener port) to known or trusted source addresses at the network perimeter or load balancer; this prevents arbitrary remote peers from reaching the listener but blocks legitimate new connections from unrestricted sources. Rate-limiting QUIC Initial packets at the firewall layer is an additional compensating control, though tuning thresholds to avoid impacting legitimate high-connection-rate clients requires careful calibration.

CVE-2014-0160 HIGH POC
7.5 Apr 07

The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe

CVE-2014-0195 MEDIUM POC
6.8 Jun 05

The dtls1_reassemble_fragment function in d1_both.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0

CVE-2014-0224 HIGH POC
7.4 Jun 05

OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph

CVE-2016-0800 MEDIUM POC
5.9 Mar 01

The SSLv2 protocol, as used in OpenSSL before 1.0.1s and 1.0.2 before 1.0.2g and other products, requires a server to se

CVE-2015-0204 MEDIUM POC
4.3 Jan 09

The ssl3_get_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k

CVE-2015-4000 LOW POC
3.7 May 21

The TLS protocol 1.2 and earlier, when a DHE_EXPORT ciphersuite is enabled on a server but not on a client, does not pro

CVE-2014-3566 LOW POC
3.4 Oct 15

The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, uses nondeterministic CBC padding, which mak

CVE-2016-2107 MEDIUM POC
5.9 May 05

The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a

CVE-2015-1793 MEDIUM POC
6.5 Jul 09

The X509_verify_cert function in crypto/x509/x509_vfy.c in OpenSSL 1.0.1n, 1.0.1o, 1.0.2b, and 1.0.2c does not properly

CVE-2022-3602 HIGH
7.5 Nov 01

A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Rated hig

CVE-2014-3470 MEDIUM
4.3 Jun 05

The ssl3_send_client_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before

CVE-2017-3730 HIGH POC
7.5 May 04

In OpenSSL 1.1.0 before 1.1.0d, if a malicious server supplies bad parameters for a DHE or ECDHE key exchange then this

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SLES15-SP5-CHOST-BYOS-SAP-CCloud Not-Affected
SLES15-SP5-CHOST-BYOS-SAP-CCloud Not-Affected
SLES15-SP6-CHOST-BYOS Not-Affected
SLES15-SP6-CHOST-BYOS Not-Affected
SLES15-SP6-CHOST-BYOS-Aliyun Not-Affected

Share

CVE-2026-14456 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy