Issue summary: When an OpenSSL QUIC server (Listener SSL object) processes valid QUIC Initial packets for unknown destination connection IDs, it can… (CVE-2026-14456)
OpenSSL QUIC server implementations prior to a fix allow unlimited allocation of new connection channels when processing valid QUIC Initial packets with unknown destination connection IDs. This can lead to unbounded memory growth if the application does not accept connections quickly enough, potentially causing a denial of service. The issue has been present since OpenSSL 3.5 when QUIC support was introduced. A fix has been implemented to limit the number of pending connections to 256 by default, configurable by the application.
AI Analysis
Technical Summary
The vulnerability arises in the OpenSSL QUIC server Listener SSL object when it processes valid QUIC Initial packets for unknown destination connection IDs. If no existing connection matches the Connection-Id, the server allocates a new channel object and queues it for acceptance by the application via SSL_accept(). Without any limit on pending connections, an attacker can cause the server to allocate memory indefinitely by sending many Initial packets faster than the application accepts them. This resource exhaustion leads to denial of service. The flaw is classified under CWE-770 (Allocation of Resources Without Limits or Throttling). The fix introduces a default limit of 256 pending connections, adjustable via SSL_set_value_uint(). The vulnerability affects OpenSSL versions starting from 3.5 when QUIC was added. The FIPS module is not affected as QUIC is outside its boundary.
Potential Impact
A remote attacker can cause the OpenSSL QUIC server to allocate memory without bounds by sending a high volume of valid QUIC Initial packets with unknown destination connection IDs. This can exhaust server memory resources, making the QUIC listener unavailable and resulting in a denial of service condition. There is no indication of code execution or data compromise from the provided information.
Mitigation Recommendations
A fix has been implemented that enforces a limit on the number of pending QUIC connections waiting to be accepted, with a default limit of 256. Applications can adjust this limit using SSL_set_value_uint(). Users should upgrade to a version of OpenSSL that includes this fix. Since no specific patched version is stated, check the official OpenSSL advisories for the fixed release. Until patched, applications should ensure they accept connections promptly to avoid resource exhaustion.
Issue summary: When an OpenSSL QUIC server (Listener SSL object) processes valid QUIC Initial packets for unknown destination connection IDs, it can… (CVE-2026-14456)
Description
OpenSSL QUIC server implementations prior to a fix allow unlimited allocation of new connection channels when processing valid QUIC Initial packets with unknown destination connection IDs. This can lead to unbounded memory growth if the application does not accept connections quickly enough, potentially causing a denial of service. The issue has been present since OpenSSL 3.5 when QUIC support was introduced. A fix has been implemented to limit the number of pending connections to 256 by default, configurable by the application.
Affected software
pkg:github/openssl/opensslRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises in the OpenSSL QUIC server Listener SSL object when it processes valid QUIC Initial packets for unknown destination connection IDs. If no existing connection matches the Connection-Id, the server allocates a new channel object and queues it for acceptance by the application via SSL_accept(). Without any limit on pending connections, an attacker can cause the server to allocate memory indefinitely by sending many Initial packets faster than the application accepts them. This resource exhaustion leads to denial of service. The flaw is classified under CWE-770 (Allocation of Resources Without Limits or Throttling). The fix introduces a default limit of 256 pending connections, adjustable via SSL_set_value_uint(). The vulnerability affects OpenSSL versions starting from 3.5 when QUIC was added. The FIPS module is not affected as QUIC is outside its boundary.
Potential Impact
A remote attacker can cause the OpenSSL QUIC server to allocate memory without bounds by sending a high volume of valid QUIC Initial packets with unknown destination connection IDs. This can exhaust server memory resources, making the QUIC listener unavailable and resulting in a denial of service condition. There is no indication of code execution or data compromise from the provided information.
Mitigation Recommendations
A fix has been implemented that enforces a limit on the number of pending QUIC connections waiting to be accepted, with a default limit of 256. Applications can adjust this limit using SSL_set_value_uint(). Users should upgrade to a version of OpenSSL that includes this fix. Since no specific patched version is stated, check the official OpenSSL advisories for the fixed release. Until patched, applications should ensure they accept connections promptly to avoid resource exhaustion.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-9x89-v382-mjh7
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-14456"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a7e0352bf8831d5398f7150
Added to database: 08/13/2026, 17:48:02 UTC
Last enriched: 08/13/2026, 17:53:46 UTC
Last updated: 08/14/2026, 00:21:20 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.