Skip to main content

OpenSSL EUVDEUVD-2026-35479

| CVE-2026-34183 HIGH
Improperly Controlled Sequential Memory Allocation (CWE-1325)
7.5
CVSS 3.1 · Vendor
Share

Severity by source

Vendor (CNA) PRIMARY
7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
SUSE
6.5 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Red Hat
7.5 MEDIUM
qualitative

Primary rating from Vendor (CNA).

CVSS VectorVendor

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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
Jun 10, 2026 - 16:26 vuln.today
Analysis Generated
Jun 10, 2026 - 16:26 vuln.today
CVSS changed
Jun 10, 2026 - 16:22 NVD
7.5 (HIGH)
CVE Published
Jun 09, 2026 - 11:43 nvd
UNKNOWN (no severity yet)
CVE Published
Jun 09, 2026 - 11:43 nvd
HIGH 7.5

Description PRE-NVD

Disclosed via GitHub release of openssl/openssl. NVD scoring and full description are pending.

AnalysisAI

Denial of service in OpenSSL QUIC implementation allows remote unauthenticated attackers to exhaust server memory by sending crafted PATH_CHALLENGE frames that trigger unbounded memory growth in the QUIC handler. The flaw affects OpenSSL branches 3.4.x, 3.5.x, 3.6.x, and 4.0.0, and is fixed in the 4.0.1 security release alongside numerous other CVEs. No public exploit identified at time of analysis and EPSS is very low (0.02%), but the network-reachable, no-auth nature of QUIC server endpoints makes the issue operationally relevant for TLS/QUIC-facing services.

Technical ContextAI

OpenSSL is the dominant cryptographic library underpinning TLS, DTLS, and the newer QUIC transport across web servers, VPNs, load balancers, and embedded stacks. The vulnerability sits inside the QUIC PATH_CHALLENGE handler, which is part of QUIC connection migration / path validation: a peer sends PATH_CHALLENGE frames, and the receiver tracks state to issue PATH_RESPONSE. CWE-1325 (Improperly Controlled Sequential Memory Allocation) maps directly to this behavior - the handler allocates state per challenge without bounding the total, so a flood of PATH_CHALLENGE frames causes memory consumption to grow without limit. Affected CPE-equivalent branches per EUVD are 3.4.0-3.4.5, 3.5.0-3.5.6, 3.6.0-3.6.2, and 4.0.0, all of which ship the new QUIC code paths added in recent OpenSSL releases.

RemediationAI

Apply the vendor-released patches: upgrade to OpenSSL 4.0.1, 3.6.3, 3.5.7, or 3.4.6 depending on the branch in use, as published in the OpenSSL security advisory at https://openssl-library.org/news/secadv/20260609.txt and the 4.0.1 release notes at https://github.com/openssl/openssl/releases/tag/openssl-4.0.1. Distribution users should pull the corresponding package update, e.g. Ubuntu via USN-8414-1 at https://ubuntu.com/security/notices/USN-8414-1, and rebuild or restart any statically linked services. Where immediate upgrade is not possible, the most effective workaround is to disable OpenSSL QUIC server support in affected applications or block inbound UDP to QUIC listeners (typically UDP/443) at the network edge - note this also disables HTTP/3 and any other QUIC-based services, degrading performance for clients that would have negotiated QUIC and falling back to TLS-over-TCP. Rate-limiting UDP/443 per source IP at a front-end load balancer is a partial mitigation that reduces but does not eliminate the memory-growth risk against distributed senders, so it should be a stopgap rather than a substitute for patching.

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-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

CVE-2016-8610 HIGH
7.5 Nov 13

A denial of service flaw was found in OpenSSL 0.9.8, 1.0.1, 1.0.2 through 1.0.2h, and 1.1.0 in the way the TLS/SSL proto

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Liberty Linux 10 Fixed
SUSE Liberty Linux 9 Fixed
openSUSE Tumbleweed Fixed
SUSE Linux Enterprise Module for Basesystem 15 SP7 Affected
SUSE Linux Enterprise Server 15 SP7 Affected

Share

EUVD-2026-35479 vulnerability details – vuln.today

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